Date: Wed, 28 Dec 2011 16:57:03 +0100 From: Dimitry Andric <dim@FreeBSD.org> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: Current FreeBSD <freebsd-current@freebsd.org>, Ports FreeBSD <freebsd-ports@FreeBSD.org> Subject: Re: /usr/local/lib/gcc46/gcc/x86_64-portbld-freebsd9.0/4.6.3/../../../libstdc++.a: could not read symbols: Bad value Message-ID: <4EFB3C4F.2020108@FreeBSD.org> In-Reply-To: <4EFAF3FC.60002@zedat.fu-berlin.de> References: <4EFAF3FC.60002@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EFB3C4F.2020108>