Ok,I have to concur with Marc - that there was no -fPIC and the necessary libraries were missing as well on my x86_64 red hat box. This seems to be happening with all the builds - perl, mod_perl, and probably apache too.
If Perl is configured OK, mod_perl gets the args from Perl and everytning goes well, the same on all normal Makefile.PL building modules.
But you must take care that the rests of things you had to use are compiled also with -fPIC.
All RedHat or Fedora default builds seems to have been compiled that way, so no problems for default libs.
(I haven't had a chance to get back to rebuilding apache as last suggested.) Different from Marc, I have been working as root, but still experiencing the same problems. The other thing I noticed was that a random directory (from the src tree) was added to the CCDLFLAGS when I added '-rdynamic -W1' during configure (as per the rpm version of perl). I had to remove this manually from the Makefile. Tom --On Wednesday, May 04, 2005 12:09 PM +0200 Marc Gràcia <[EMAIL PROTECTED]> wrote: > El dl 02 de 05 del 2005 a les 10:05 -0700, en/na Stas Bekman va > escriure: > > > > Marc Gràcia wrote: >> I had some problems like this on my new x86_64 machine with >> mod_perl2, seems that not only perl must be compiled with -fPIC >> , also apache and all libraries or modules you plan to use. I >> think it's a general issue with this architecture, not mod_perl >> related. > > That's correct, Marc. > >> If not, there are runtime linking relocation errors everywhere.. >> (I also had to recompile with -fPIC db and libz, for example) >> Maybe that's the problem... > > I supposed that Tom has recompiled everything after rebuilding > perl. > mod_perl will pick up -fPIC automatically at compile time, if > perl was > compiled with it. > > > Yes that's Ok for all perl modules. > But BTW, my Perl Compilation did not put automaticaly the -fPIC > flag when configuring and also didn't detect the needed libraries > (The line when Config script lets you add additional libraries > was empty except for the ones i compiled for myself, see below). > I had to put all that manually (After a lot of recompilations > trying to find what was happening) > > I was using a closed environment in a user with no root > permissions. All dependencies except most basic ones > (libc,lpthreads,etc..) are compiled and self contained in the > user's home (I'm doing a untar-and-forget instalation for our > product). > The same procedure went OK on all other kind of machines... so > maybe perl Config has some problem with x86_64. > The base system was a Fedora Core 3 EM64T version with no 32bits > compatibility packages installed. > But everything is running OK after all, only the Configure script > failed.. > > > > > > > > > -- > Marc Gràcia <[EMAIL PROTECTED]> Tom Caldwell Vanderbilt University Medical Center
