On 2011-12-28 11:48, O. Hartmann wrote:
...
/usr/local/bin/ld:
/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a(functexcept.o):
relocation R_X86_64_32 against `std::bad_exception::~bad_exception()'
can not be used when making a shared object; recompile with -fPIC
/usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a:
could not read symbols: Bad value
collect2: ld returned 1 exit status
What happens if you compile and link the following simple program with
g++46:
#include <iostream>
int main(void)
{
std::cout << "Hello World!" << std::endl;
return 0;
}
Does it fail with the same type of link error, e.g. linking to the
libstdc++.a instead libstdc++.so? It would be nice if you can add -v to
the command line, and paste the output here.
I suspect your g++46 port is busted, for some reason.
_______________________________________________
freebsd-current@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
