Yes that's Ok for all perl modules.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.
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]> |
