This is the mail archive of the
libstdc++@sourceware.cygnus.com
mailing list for the libstdc++ project.
Re: configure doesn't work today
- To: Philip Martin <pm at corris dot dircon dot co dot uk>
- Subject: Re: configure doesn't work today
- From: Benjamin Kosnik <bkoz at cygnus dot com>
- Date: Mon, 14 Feb 2000 14:05:56 -0800 (PST)
- cc: libstdc++ at sourceware dot cygnus dot com
You can still build with this, even though it looks frightening.
config-ml.in is needed to make multilibs work. This file is in the
top-level gcc distro...
The end result is that I'd like to move libstdc++-v3 from being a
"stand-alone" project that one can download and build without any other
tweaking to something that relies on an existing gcc source directory.
Yes this is a pain, but doing this allows v-3 to do things like build
multi-libs, and work with cross compilers. FWIW, this functionality is
necessary for v-3 to replace v-2.
The end goal is to have v-3 be more of a "plug-in" replacement for the
current v-2 distro. You'll need to re-arrange your source and build
trees a bit because of this:
1) get the gcc-2.95.2 distro
2) unpack
3) cd gcc-2.95.2; mv libstdc++ libstdc++-v2
4) copy over your libstdc++-v3 sources to the gcc-2.95.2 toplevel source dir.
ie
cd ..
cp -R libstdc++ gcc-2.95.2/libstdc++-v3
5) link correct library sources to "libstd++"
ie
cd gcc-2.95.2
ln -s libstdc++-v3 libstdc++
You'll now be able to build just the library, but will need to
re-configure with this new info
I know this is a pain.
-Benjamin
> creating src/Makefile
> creating math/Makefile
> creating libio/Makefile
> creating config.h
> ./config.status: /../config-ml.in: No such file or directory