The first AMD64 issue:
gcc -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -O6 -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -DUNIX -I . -I ../../../pd/src -I ../shared -c -o hammer/accum.o hammer/accum.c gcc -o /home/users/e/ei/eighthave/cvs/pure-data/packages/linux_make/build// usr/local/lib/pd/extra/cyclone/accum.pd_linux -Wall -W -Wstrict-prototypes -Wno-unused -Wno-parentheses -Wno-switch -O6 -funroll-loops -fomit-frame-pointer -fno-strict-aliasing -DUNIX -I . -I ../../../pd/src -I ../shared -export_dynamic -shared hammer/accum.o /usr/bin/ld: hammer/accum.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC hammer/accum.o: could not read symbols: Bad value
Shouldn't all externals be compiled with -fPIC on Linux? I know Darwin/Mac OS X compiles DLLs as -fPIC by default.
.hc
________________________________________________________________________ ____
¡El pueblo unido jamás será vencido!
On Wed, 30 Nov 2005, Hans-Christoph Steiner wrote:
/usr/bin/ld: hammer/accum.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC hammer/accum.o: could not read symbols: Bad value Shouldn't all externals be compiled with -fPIC on Linux? I know Darwin/Mac OS X compiles DLLs as -fPIC by default.
What's the effect of -fPIC and -fpic in 32-bit mode on PC ? Are these options ignored or do they have some slight effect that I don't know about?
____________________________________________________________________ Mathieu Bouchard - tél:+1.514.383.3801 - http://artengine.ca/matju Freelance Digital Arts Engineer, Montréal QC Canada
On Nov 30, 2005, at 1:32 AM, Mathieu Bouchard wrote:
On Wed, 30 Nov 2005, Hans-Christoph Steiner wrote:
/usr/bin/ld: hammer/accum.o: relocation R_X86_64_32 against `a local symbol' can not be used when making a shared object; recompile with -fPIC hammer/accum.o: could not read symbols: Bad value Shouldn't all externals be compiled with -fPIC on Linux? I know Darwin/Mac OS X compiles DLLs as -fPIC by default.
What's the effect of -fPIC and -fpic in 32-bit mode on PC ? Are these options ignored or do they have some slight effect that I don't know about?
I was under the impression that -fPIC should be used on shared libraries for Linux as well, I think Günter said something to that effect some time ago. I don't have anything to back that up other than a recollection.
.hc
________________________________________________________________________ ____
"[W]e have invented the technology to eliminate scarcity, but we are deliberately throwing it away to benefit those who profit from scarcity." -John Gilmore
-
Hans-Christoph Steiner -
Mathieu Bouchard