This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: DESTDIR vs. libstdc++
- To: Marc dot Espie at liafa dot jussieu dot fr
- Subject: Re: DESTDIR vs. libstdc++
- From: Tom Tromey <tromey at redhat dot com>
- Date: 04 Jul 2001 11:41:39 -0600
- Cc: gcc-bugs at gcc dot gnu dot org, gcc at gcc dot gnu dot org
- References: <20010704141244.A631@schutzenberger.liafa.jussieu.fr>
- Reply-To: tromey at redhat dot com
>>>>> "Marc" == Marc Espie <espie@schutzenberger.liafa.jussieu.fr> writes:
Marc> I'd like this solved at some point. The hairy parts are:
Marc> - cygnus configure is totally blind to DESTDIR.
I don't think Cygnus configure needs to know anything about DESTDIR.
Instead I think it is a matter of changing every Makefile.in (except
those generated by automake) to respect it.
Marc> - cross-compiles.
What is the problem here? I'm curious because if there is some
conflict I want to make sure that automake does the right thing.
Note that most GNU-style Makefiles work if you run configure with a
given --prefix and then change it at `make install' time:
/gcc/configure --prefix=/whatever
make
make install prefix=/destdir/whatever
This was common practice in GNU for a long time (this method is also
supported by automake). I don't recall if it is in the GNU coding
standards (many things like this are not). I also don't know if this
is supported by the gcc Makefiles.
Tom