"Denis Bueno" <dbueno@xxxxxxxxx> writes:
> I'm on OS X 10.4.11 on Intel using git 1.5.5.3.
>
> I'd been trying to use the git-instaweb script (both with and without
> arguments) with lighttpd (which I installed through Macports) without
> success, seeing the following kind of bizarre error message:
>
> funsat[290] > git instaweb
> /opt/local/bin/git-instaweb: line 6033: /usr/bin/env perl: No such
> file or directory
> 2008-06-13 09:09:31: (log.c.75) server started
>
> funsat[291] > 2008-06-13 09:09:31: (mod_cgi.c.998) CGI failed:
> Exec format error /Volumes/work/funsat/.git/gitweb/gitweb.cgi
> mod_cgi.c.1001: aborted
> 2008-06-13 09:09:31: (mod_cgi.c.584) cgi died, pid: 23237
>
> "/usr/bin/env perl: No such file or directory"? Huh? I certainly have
> perl installed, so I don't know what that's about.
>
> That line simply calls perl by the $PERL variable, which is set at the
> top of the script, like so:
>
> PERL='/usr/bin/env perl'
This depends on how git was build (on compile time configuration).
git-instaweb.sh (source of git-instaweb) has
PERL='@@PERL@@'
which is set to value of $PERL_PATH (or, to be more exact, its squoted
version) during building git-instaweb. So you can simply use
$ make PERL_PATH=/usr/bin/perl
# make PERL_PATH=/usr/bin/perl install
or whatever, or you can use ./configure script
$ make configure
$ ./configure --with-perl=/usr/bin/perl
On Linux for example the path to perl is set explicitely, instead of
using "/usr/bin/env perl" construct. The 'env' construct has the
following disadvantages:
- it uses first Perl find in your $PATH, so if git works for you or
don't work depends on user's personal configuration
(reproductability, convenience and security).
- AFAIK it doesn't allow to pass switches to Perl
P.S. Check if you have new enough Perl (there are problems with
Unicode support in old Perl), and if you have CGI.pm new enough
installed for gitweb.
--
Jakub Narebski
Poland
ShadeHawk on #git
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
