problem "make"ing gtk+ "/usr/bin/env: perl -w"
I'm trying to install gtk+-2.6.8, but am getting a make error (with several other packages also).
The error is
/usr/bin/env: perl -w: No such file or directory
make: *** [s-enum-types-h] Error 127
make: Leaving directory '/home/caid/downloads/gtk+-2.6.8/gdk-pixbuf'
I'm using kernel 220.127.116.11 on Slackware 10.0, with perl 5.8.7.
I've been googling like mad all night, and have found a lot of references to the limitations of the Berkeley #! hack with 'perl -w' being parsed as a single argument.
I've trawled through all of the gtk perl scripts, replacing any reference to perl -w with use warnings; instead, but make still keeps complaining about perl -w being invalid.
How do I get round this? I haven't seen any other complaints like this with regards to building gtk+-2.6.8, am I the only one having this problem?
Thanks in advance
The #! line is interpreted by the shell, which in turn is set by reading /etc/passwd when you log in. You might try changing your login shell to GNU BASH (www.gnu.org).
thanks for your reply, but my shell is already bash.
Still haven't found a fix for this, it's slowly driving me mad.
I've cat-ed every file in the gtk install through grep looking for /usr/bin/perl, checked all the env variables for a reference to perl, and found nothing. i can only think that it's looking at an outside script, but don't know where else to look.
Any help would be much appreciated.
Assumming your Perl is in /usr/bin you should be able to replace the env command with
The env in this case exists in case you have Perl installed to someplace out of the way (it will try to find it).
thanks a lot for your replies.
i pulled down the gtk+ 2.7.4 source and tried making that.
unfortunately I've got a new, different problem.
the build is now requiring cairo >= 0.5.2-head
but I can't find a -head version anywhere.
If I install cairo 0.5.2, it says:
Requested 'cairo >= 0.5.2-head' but version of cairo is 0.5.2
Re: problem "make"ing gtk+ "/usr/bin/env: perl -w"
Could you possibly post some links to the sites you found on Google? Maybe we can find or deduce something that you missed.
Re: hi there
thanks for your help.
managed to get it all ship-shape. ended up moving the /bin/env executable so the mystery script couldn't find it. the resulting error gave the script file name, and once i had that i could happily remove the bad call to env.
feel like a moron for making such hard work of it, but you get that. or at least i do ;o)
|All times are GMT -5. The time now is 04:42 AM.|