Date: Tue, 29 Jun 2010 09:44:40 -0400 From: Eitan Adler <lists@eitanadler.com> To: Boris Kochergin <spawk@acm.poly.edu> Cc: freebsd ports <freebsd-ports@freebsd.org> Subject: Re: Confirming a bug in clang++ (freeBSD Message-ID: <AANLkTil-g_TrS_lZs75BfAotTJE4x67tloippJAz8H6V@mail.gmail.com> In-Reply-To: <4C29796C.7070901@acm.poly.edu> References: <AANLkTink7JcqKh4J2Q72CsQ3J-DqYagSB0izFho5GnYX@mail.gmail.com> <4C297844.2030500@acm.poly.edu> <4C29796C.7070901@acm.poly.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
>>> My bug report is here: http://llvm.org/bugs/show_bug.cgi?id=3D7489 >>> >>> I want to know if this is my problem or a clang++ problem or a bug >>> somewhere else. >>> >> >> Works fine here: >> >> # uname -a >> FreeBSD peer 8.0-RELEASE-p2 FreeBSD 8.0-RELEASE-p2 #2: Mon Feb 22 23:18:= 53 >> EST 2010 =C2=A0 =C2=A0 root@peer:/usr/obj/usr/src/sys/PEER =C2=A0i386 >> >> # clang++ -v >> clang version 1.1 (branches/release_27) >> Target: i386-portbld-freebsd8.0 >> Thread model: posix >> >> I can try it on a recent CURRENT machine tomorrow, but perhaps you'd bes= t >> share your environment. I've compiled non-trivial C++ programs with clan= g++ >> and they've behaved properly. >> >> -Boris >> > One difference I notice between your environment and mine is that, accord= ing > to your bug report, your program links against > /usr/local/lib/gcc46/libstdc++.so.6, while mine links against > /usr/lib/libstdc++.so.6. > > -Boris > I forgot about that. I use gcc46 to build ports and have libstdc++.so.6 gcc46/libstdc++.so.6 in /etc/libmap.conf I guess I should close the bug. --=20 Eitan Adler
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTil-g_TrS_lZs75BfAotTJE4x67tloippJAz8H6V>