Date: Sat, 11 May 2002 11:15:52 -0700 From: "David O'Brien" <obrien@FreeBSD.org> To: Alfred Perlstein <alfred@FreeBSD.org> Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/lib/libc_r/uthread Makefile.inc uthread_autoinit.c uthread_autoinit.cc Message-ID: <20020511111552.B12326@dragon.nuxi.com> In-Reply-To: <200205110813.g4B8Dgo23554@freefall.freebsd.org>; from alfred@FreeBSD.org on Sat, May 11, 2002 at 01:13:42AM -0700 References: <200205110813.g4B8Dgo23554@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, May 11, 2002 at 01:13:42AM -0700, Alfred Perlstein wrote: > Modified files: > lib/libc_r/uthread Makefile.inc > Added files: > lib/libc_r/uthread uthread_autoinit.c > Removed files: > lib/libc_r/uthread uthread_autoinit.cc Why didn't you ask for a repo copy? Please stop always being in such a rush. > Log: > Use GCC's __attribute__ ((constructor)) mechanism to invoke the pthread > startup code rather than a static C++ object since c++ seems to be broken. Please bother to take the time to learn about the situation. c++ (the compiler) is NOT broken. You don't have any C++ support libs right now. THAT is why you get unresolved references. In fact, the unresolved reference you get is due to the C++ ABI versioning that the GNU people added just so upgrades of the C++ compiler will not "break" your existing libs. Everything in the tree built, so the only way the state of libc_r could bother is in your own code. This really is not the time to be using -CURRENT for anything other than programming w/in /usr/src. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20020511111552.B12326>