On 2 Oct 2008, at 15:45, Gregory Weston wrote:
<logs.tar.gz>
Linking library libgnustep-base ...
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../x86_64-suse-linux/
bin/ld: /usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../lib64/
libbfd.a(format.o): relocation R_X86_64_32 against `a local symbol'
can not be used when making a shared object; recompile with -fPIC
/usr/lib64/gcc/x86_64-suse-linux/4.3/../../../../lib64/libbfd.a:
could not read symbols: Bad value
collect2: ld returned 1 exit status
This means that the libbfd on your system was badly built so that it
cant be linked into a shared library.
Your options are either to get/build libbfd complied with -fPIC as the
error message suggests, or to configure the base library with --
disable-bfd to that the library builds without using libbfd.
If you don't use libbfd, the base library will be unable to display
the names of methods/functions in a stacktrace after an exception.
Probably not a big issue for you.
_______________________________________________
Bug-gnustep mailing list
[email protected]
http://lists.gnu.org/mailman/listinfo/bug-gnustep
