> From: Jeff Beard <[EMAIL PROTECTED]>
> Date: Mon, 08 Jan 2001 12:48:58 -0700 (MST)
> Subject: Re: mod-perl on Solaris 2.6
>
> Check out the mailing list archive for something I posted
> a while back. It boiled down to not using GNU binutils for
> anything. Including GCC.
Partly, I agree. Gcc is fine for Solaris 2.5, 7 and 8, if you use the package from
sunfreeware.com, and install all relevant patches. Don't use any other gnu bintools
though, especially not the linker. (Well, at least not with a "stock" Solaris system.
:) I have been building perl for years with that combo, and mod_perl/Apache for just
over a year, and while it does require that you know what you are doing, (and it
certainly sounds like Siddhartha does), it always works fine for me.
Siddhartha, have you tried the $HOME/.makepl_args.mod_perl file-method to build
mod_perl/Apache?? If you set this file up properly, you can build/install
mod_perl/Apache with the standard:
perl Makefile.pl
make
make test
make install
all from within the mod_perl distribution dir. This is documented in the INSTALL
document of the mod_perl distribution, and there is a commented sample/template in
eg/makepl_args.mod_perl (note there is no leading . here) of the distribution. (And
once Doug relases another version of mod_perl with no _ in the version number, you
will be able to do "install mod_perl" from the CPAN shell, which downloads and builds
the latest versions of everything, hopefully:)
Also, make sure your LD_LIBRARY_PATH and PATH vars are set properly. (I have never
had to use the LD_PRELOAD var, and I build a lot of software for Solaris from C
source) If you use tcsh, (or any shell that supports it) try "which perl" and "which
gcc", and "whereis perl" and "whereis gcc", and make sure that you are really getting
what you think. And make sure that any sym-links/links (like maybe /usr/bin/perl)
point to where you want them. I always try to make sure that my build environments
can only see what I want them to see, and no other versions of anything.
One other thing, look at the output of perl -V, and see if the flags to gcc for
building perl are the same as what are being passed to gcc for building
mod_perl/Apache. They should be, but something might be screwing them up in your
enviornment, so check anyway. :)
David McCabe Unix System Administrator
Le Groupe Videotron [EMAIL PROTECTED] (514) 380 4433
"We've all heard that a million monkeys banging
on a million typewriters will eventually reproduce
the works of Shakespeare. Now, thanks to the
Internet, we know this is not true."
- Robert Wilensky UCB
