jfm wrote:
./admin/cvs.sh: /sw/bin/autoheader-2.59: /sw/bin/perl: bad
interpreter: No such file or directory *** AUTOHEADER NOT FOUND!.
This type of thing is due to having at some time used a perl-xyz from
fink, (in this case when last building autoconf2.5 _ but many other
pkgs have the problem),
Jean-Francois,
I'm not sure if it's the same error you are seeing, but one bug I am aware
of is this: there is a place in the fink code where fink tests to see
which is the current version of perl installed on the system... unfortnately,
fink seems to cache this value in the database. So if you
you end up with a
*real* perl581, but a *virtual* perl581-core, and get this error.
Well, that can't be the right explanation, because there isn't a real
perl581 package at all.
-- Dave
---
This SF.Net email sponsored by Black Hat
On Jun 23, 2004, at 10:54 PM, David R. Morrison wrote:
Jean-Francois,
I'm not sure if it's the same error you are seeing, but one bug I am
aware
of is this: there is a place in the fink code where fink tests to see
which is the current version of perl installed on the system...
unfortnately,
Sorry, I meant add or remove a perl package not add or remove a fink
package...
---
This SF.Net email sponsored by Black Hat Briefings Training.
Attend Black Hat Briefings Training, Las Vegas July 24-29 -
digital self defense, top technical
On Jun 23, 2004, at 10:51 PM, David R. Morrison wrote:
you end up with a
*real* perl581, but a *virtual* perl581-core, and get this error.
Well, that can't be the right explanation, because there isn't a real
perl581 package at all.
Correct .
It is due to the fact that a number of pkgs install
On Jun 23, 2004, at 10:57 PM, jfm wrote:
It is due to the fact that a number of pkgs install scripts beginning
with
#!/currently/active/perl
More accurately probably,
#! `which perl`
Cf all
'checking for perl... /sw/bin/perl'
in log files
JF
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote:
More accurately probably,
#! `which perl`
#! /usr/bin/env perl
which will actually work. There are a lot of strange restrictions on
that line.
Dave Brown
---
This SF.Net email
David Brown wrote:
On Thu, Jun 24, 2004 at 12:18:51AM +0200, jfm wrote:
More accurately probably,
#! `which perl`
#! /usr/bin/env perl
which will actually work. There are a lot of strange restrictions on
that line.
Most of these packages allow the user to override their tests for perl by
