Stas and Marc,
So after a week hiatus I was finally able to return to my Perl/ModPerl2/Apache2 woes on my Dell 64bit box running redhat linux.
When we last left the main saga, I had just rebuilt perl and modperl with the -fPIC flag only to find that the tests for subprocess.t would not work. I tried several suggestions from Stas but nothing worked. Mark suggested recompiling apache as well and that was to be my next step before I was sidelined by other issues.
When I rebuilt apache today, the modperl tests still failed at subprocess.t even after another modperl rebuild. So I did another reinstall of perl. This time during the configure operation when the script prompted for directories to search for standard libs the defaults were /usr/local/lib /lib /usr/lib (as before). After checking out the original redhat installed version of perl (from rpm vesion 5.8.0), I noticed that it used mostly libs from /lib64 and /usr/lib64. So I overrode the defaults for this question with - /lib /usr/lib /lib64 /usr/lib64. Then when I got to the prompt for default libs it had all the ones I needed as the default value which it had failed to do before. I still had to change the link flags from -fpic to -fPIC and replace the default link switches with values I found in the redhat perl, but then all of the tests for perl and modperl passed.
I did not even have to rebuild apache after that.
So, thanks for all your help,
Tom
--On Thursday, May 05, 2005 10:23 PM -0700 Stas Bekman <[EMAIL PROTECTED]> wrote:
Marc Grącia 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, you may want to ask perl5-porters to help you with this issue. As you have figured out, mod_perl just picks perl's flags, so it's a perl issue.
-- __________________________________________________________________ Stas Bekman JAm_pH ------> Just Another mod_perl Hacker http://stason.org/ mod_perl Guide ---> http://perl.apache.org mailto:[EMAIL PROTECTED] http://use.perl.org http://apacheweek.com http://modperlbook.org http://apache.org http://ticketmaster.com
Tom Caldwell Vanderbilt University Medical Center
