This is the mail archive of the
libstdc++@sources.redhat.com
mailing list for the libstdc++ project.
Re: Again: Bootstrap failure for objdir containing colon
- To: Alexandre Oliva <aoliva at redhat dot com>
- Subject: Re: Again: Bootstrap failure for objdir containing colon
- From: Gerald Pfeifer <pfeifer at dbai dot tuwien dot ac dot at>
- Date: Sat, 16 Dec 2000 17:58:47 +0100 (CET)
- cc: <gcc at gcc dot gnu dot org>, <libstdc++ at gcc dot gnu dot org>, Geoffrey Keating <geoffk at redhat dot com>
On 16 Dec 2000, Alexandre Oliva wrote:
> I don't see any difference here. What's the difference between your
> storing your build tree in /tmp/`date`/gcc and my storing my source
> tree in ~/src/`date`/gcc-cvs? Any Makefile target that refers to
> $(srcdir) will break, then.
Oops, clearly I misunderstood! I thought you were referring to sub-
directories *within* our source tree. Obviously you're right, sorry.
> Because libstdc++-v3 is the first package (AFAIK) that exports its
> build parameters (header and library search paths), as opposed to
> having them hard-coded in the top-level build machinery.
I assume the advantages of this approch outweigh the disadvantages?
In the worst case, we probably should check for colons in objdir
or srcdir during configure time and back out with a clear warning
then, instead of failing near the end of the build...
Gerald
--
Gerald "Jerry" pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/