Fred Moyer wrote:
William A. Rowe, Jr. wrote:
Bianca Taylor wrote:
/bin/ld:
/tmp/unisolve/perl/lib/5.8.8/x86_64-linux/auto/DynaLoader/DynaLoader.a(DynaLoader.o):
relocation R_X86_64_32 against `a local symbol' can not be used when
making a shared object; recompile with -fPIC
/tmp/unisolve/perl/lib/5.8.8/x86_64-linux/auto/DynaLoader/DynaLoader.a:
could not read symbols: Bad value
collect2: ld returned 1 exit status
make[1]: *** [mod_perl.so] Error 1
make[1]: Leaving directory
`/home/unisolve/mod_perl-2.0.4/src/modules/perl'
make: *** [modperl_lib] Error 2
Perl itself makes several bad calls w.r.t. CFLAGS, LDFLAGS, SHLDFLAGS
etc,
that are propagated also into config_heavy.pl. On several platforms I've
noted that -fPIC is ignored, on others I've noted that specific flag
values
are dropped for the building of shared libs.
It's a matter of working backwards from modperl's build into the config
script of perl to determine where perl went wrong.
The solution should be as easy as recompiling perl with -fPIC. Here's a
link to the list archives where this has been discussed in detail.
http://www.gossamer-threads.com/lists/engine?list=modperl;do=search_results;search_forum=forum_8;search_string=fpic;search_type=AND&sb=post_time
Of course, that's what it says above. My point is, I've had perl yank -fPIC
from my demands on the build on PPC arch. Mighty kind of it, eh?
