This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: Fallout (mostly runtime library-related) from GCC version numberchange (take two)
- From: Paolo Carlini <pcarlini at suse dot de>
- To: Zack Weinberg <zack at codesourcery dot com>
- Cc: gcc-patches at gcc dot gnu dot org, libstdc++ at gcc dot gnu dot org,java-patches at gcc dot gnu dot org, fortran at gcc dot gnu dot org
- Date: Fri, 18 Mar 2005 01:45:39 +0100
- Subject: Re: Fallout (mostly runtime library-related) from GCC version numberchange (take two)
- References: <87is3pnab0.fsf@codesourcery.com> <423A0FA1.1090700@suse.de> <87ekedn6a4.fsf@codesourcery.com>
Zack Weinberg wrote:
It appears so. At least, my trial 'make install' (done, note, without
--enable-version-specific-runtime-libs) appears to have created a
correct directory tree. If you could tell me which files are being
installed incorrectly for you, I can check that they are installed
correctly with my patch.
Sure and easy.
What happens here, on x86-linux, for a very simple
--prefix=/usr/local/gcc-exp configure, is that the whole set of
libstdc++ headers, that should be installed under
/usr/local/gcc-exp/include/c++/4.1.0/, ends up inside
/usr/local/gcc-exp/include/c++/const/
Of course not even "Hello World" compiles anymore...
Thanks,
Paolo.
P.S. Given my timezone, I will not be able to provide more feedback
before tomorrow.