> in ".o". Example: gcc -fPIC -c -I<java-header-path> file1.c -o
Based solely on looking at other peoples makefiles and code, I've been
using -fpic under linux and -fPIC under solaris.
The gcc man pages say the following:
-fpic If supported for the target machines, generate po
sition-independent code, suitable for use in a
shared library.
-fPIC If supported for the target machine, emit position-
independent code, suitable for dynamic linking,
even if branches need large displacements.
I'm not completely sure I understand the differences here. Does anyone
know what the effect of interchanging -fpic and -fPIC really is?
Cheers, Craig
------
"If God had intended Man to Watch TV, He would have given him Rabbit
Ears."
======================================================================
Craig Taverner ------====== Email:[EMAIL PROTECTED]
ComOpt AB ------======== Tel: +46-42-212580
Michael Löfmans Gata 6 ------========== Fax: +46-42-210585
SE-254 38 Helsingborg ------======== Cell: +46-708-212598
Sweden ------====== http://www.comopt.com
======================================================================
