Date: Mon, 8 Apr 2002 07:00:16 +0200 (CEST) From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at> To: "M. Warner Losh" <imp@village.org> Cc: peter@freebsd.org, <cvs-committers@freebsd.org>, <cvs-all@freebsd.org> Subject: Re: cvs commit: src/gnu/usr.bin/gperf Makefile src/gnu/usr.bin/groff/src/devices/grodvi Makefile src/gnu/usr.bin/groff/src/devices/grohtml Makefile src/gnu/usr.bin/groff/src/devices/grolbp Makefile sr Message-ID: <Pine.BSF.4.44.0204080648390.76282-100000@naos.dbai.tuwien.ac.at> In-Reply-To: <20020407.172929.32777631.imp@village.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 7 Apr 2002, M. Warner Losh wrote: > Peter Wemm <peter@FreeBSD.org> writes: >: Add -lstdc++ to the link args for these C++ tools so that they can be >: compiled with gcc-3.1. Somebody thought it was a good idea to move >: the implementation of new and delete from libgcc to libstdc++. This >: change doesn't harm the current compiler in the tree. > Is this a band-aid until the compiler can be fixed, or a real solution > long term? If I'm right, the problem is that the gcc driver is used to compile these C++ sources. One of the differences between gcc and g++ is that the latter automagically links in libstdc++ while the former does not. This has been the case since (at least GCC 2.95), but we did get away with it because, as Peter observed, new/delete have been in libgcc which got linked in anyway. GCC 3.0 and 3.1, however, have new/delete in libstdc++; the proper fix long-term would be using the g++ driver instead of the gcc driver for these C++ sources. Gerald -- Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/ 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?Pine.BSF.4.44.0204080648390.76282-100000>