[sorry my email client dropped the list from the thread, my bad] > From: "Fred Moyer" <[EMAIL PROTECTED]> > >> On Fri, 13 Jul 2007 10:26 am, Octavian Rasnita wrote: >>> From: "Geoffrey Young" <[EMAIL PROTECTED]> >>>>> /usr/lib64/gcc/x86_64-suse-linux/4.1.0/../../../../x86_64-suse-linux/bin/ld: >>>>> /usr/local/perl_588/lib/CORE/libperl.a(gv.o): relocatio >>>>> n R_X86_64_32S against `a local symbol' can not be used when making a >>>>> shared object; recompile with -fPIC >>>> >>>> the first google match for "recompile with -fPIC" and mod_perl gives >>>> what looks to be the answer. >>>> >>>> archives++ >>>> >>>> --Geoff >>> >>> I have already compiled perl with -fpic and then with -fPIC, but it >>> still >>> gives the same error when compiling mod_perl. >> >> Are you sure that you are compiling mod_perl with the fpic enabled perl >> and not your system perl? I ran into this exact same issue on x86_64 >> and >> fpic worked here. Its been a while since I did that but I don't >> remember >> there being any other gotchas. > > I did: > > $ which perl > /usr/bin/perl > $ ls -l /usr/bin/perl
so you replaced your system perl with a version that you compiled, you probably want to avoid doing that since other programs on your system might depend on that specific compilation. Instead use -DPrefix to specify a different location for the new perl you compile, and then /path/to/my/perl Makefile.PL to compile mod_perl > And it shown a link to the perl I've just installed using -fPIC. > > And I've starting compiling mod_perl using: > > $ perl Makefile.PL MP_APXS=/usr/local/apache2/bin/apxs > > Then on "make" it gave that error. Getting a good build of perl under x86_64 can be a bit tricky, when you compile perl you need to make sure that the default directories to search includes /usr/lib64. It took me a few tries to get it right, I posted my experiences here - http://use.perl.org/~Phred/journal/31581 Here's another good link I found on the subject - http://mail-archives.apache.org/mod_mbox/perl-modperl/200505.mbox/[EMAIL PROTECTED] I'd say take another few tries at it and make sure to pay extra close attention to the default search path when compiling perl - it can be done! > > I have also tried using Active State's Active Perl binary for X86_64, with > the same results. > > (I had previously renamed the folder /usr/lib/perl5 to /usr/lib/old_perl5 > for beeing sure that the system perl won't be found). > > If I'd knew that Apache, Perl and MySQL will run well on a 32 bit OS on a > 64 > bit machine, I'd install a 32 bit OS, but I heard that a 32 bit OS runs > slower on a 64 bit processor, even slower than on a 32 bit processor. > > I don't know what to do. > > Octavian > >