public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Russell VT <russellvt@gmail.com>
To: Eyal Rozenberg <eyalroz1@gmx.com>
Cc: cygwin <cygwin@cygwin.com>, Jari Aalto <jari.aalto@cante.net>
Subject: Re: cloc: hashbang header has "perl" twice
Date: Sat, 25 Sep 2021 03:59:38 -0700	[thread overview]
Message-ID: <CANV2+nU9eGVk+5uTsLB97Cqw2M4fFNU=mM-i+YTsUsoLi72++w@mail.gmail.com> (raw)
In-Reply-To: <CANV2+nVDS9FaC42DigOHAdjm0rXrcahU87kbKEy8-bFWqfNLVQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2814 bytes --]

Replying to add the package maintainer, as-per Cygwin's source distribution
files.

This would be something I'd consider installing directly from source,
though it looks like the upstream may not make that *quite* as easily as
one would like... but, I'll take a better look, after I've slept (HaHa).

Cheers -
RVT


On Sat, Sep 25, 2021 at 3:32 AM Russell VT <russellvt@gmail.com> wrote:

> Looking at the current Cygwin source, the she-bang is actually:
>
> #!/usr/bin/env perl
>
>
> ...which means it's going to pick up the first perl interpreter in your
> path.
>
> You can confirm this in the cloc code, itself, as well.
> <https://github.com/AlDanial/cloc/blob/244c1e619c2b9ea3b7be10ebdb23ecd5b6ee1361/cloc>
>
> Please note that, because this is a Perl module, you can likely just
> uninstall the Cygwin package, and then use something like "CPAN install
> cloc" to get the latest version in your perl environment (HIGHLY recommend
> to install this in your local perl modules, under your home directory).
>
> That said, it looks like someone screwed the pooch on the Cygwin
> installer... I installed it via the Cygwin setup utility and have confirmed
> your findings. It *SHOULD* be safe to just manually change the she-bang to
> "env," if you want to use the Cygwin package, directly.
>
> [image: image.png]
>
> Cheers -
> Russell VT
>
>
> On Sat, Sep 25, 2021 at 12:36 AM Eyal Rozenberg via Cygwin <
> cygwin@cygwin.com> wrote:
>
>> I'm not sure how bug reporting "etiquette" works here on the list, but -
>> I was sort of expecting an acknowledgement. Or - was I wrong to post my
>> bug report here in the first place?
>>
>> I have another bug (two actually) to report regarding meld, and I want
>> to get that report right and not have it lost in the noise.
>>
>> Eyal
>>
>> On 22/09/2021 17:20, Eyal Rozenberg via Cygwin wrote:
>> > I'm using:
>> >
>> > Package              Version                        Status
>> > cloc                 1.82+20190726+git608f376-1     OK
>> >
>> > updated today. The first line of /usr/bin/cloc is:
>> >
>> > #!/usr/bin/perl perl
>> >
>> > while it should just be:
>> >
>> > #!/usr/bin/perl
>> >
>> > (like it is on my Linux machine)
>> >
>> > Obviously this causes an error when running cloc:
>> >
>> > Can't open perl script "perl": No such file or directory
>> >
>> >
>> > I would also suggest that you consider using a newer version of cloc, as
>> > there have been several releases since 1.82
>> >
>> > Eyal
>> >
>>
>> --
>> Problem reports:      https://cygwin.com/problems.html
>> FAQ:                  https://cygwin.com/faq/
>> Documentation:        https://cygwin.com/docs.html
>> Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple
>>
>
>
> --
> Russell M. Van Tassell <russellvt@gmail.com>
>


-- 
Russell M. Van Tassell <russellvt@gmail.com>

[-- Attachment #2: image.png --]
[-- Type: image/png, Size: 21224 bytes --]

      reply	other threads:[~2021-09-25 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-22 14:20 Eyal Rozenberg
2021-09-25  7:34 ` Eyal Rozenberg
2021-09-25 10:32   ` Russell VT
2021-09-25 10:59     ` Russell VT [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CANV2+nU9eGVk+5uTsLB97Cqw2M4fFNU=mM-i+YTsUsoLi72++w@mail.gmail.com' \
    --to=russellvt@gmail.com \
    --cc=cygwin@cygwin.com \
    --cc=eyalroz1@gmx.com \
    --cc=jari.aalto@cante.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).