Re: cloc: hashbang header has "perl" twice

[Russell VT via Cygwin]

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  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.
> 
>
> 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  VersionStatus
>> > 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 
>


-- 
Russell M. Van Tassell 

-- 
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

Re: cloc: hashbang header has "perl" twice

[Russell VT via Cygwin]

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.


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  VersionStatus
> > 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 

-- 
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

Re: cloc: hashbang header has "perl" twice

[Eyal Rozenberg via Cygwin]

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