This is the mail archive of the
libstdc++@gcc.gnu.org
mailing list for the libstdc++ project.
Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- To: rittle at labs dot mot dot com
- Subject: Re: PR4114, 4113, 4082, 4078, (part of) 4096 plus other reports in gcc-bugs
- From: Neil Booth <neil at daikokuya dot demon dot co dot uk>
- Date: Fri, 24 Aug 2001 23:16:32 +0100
- Cc: libstdc++ at gcc dot gnu dot org, ungaro at pegasus dot fmrp dot usp dot br,partain at dcs dot gla dot ac dot uk, ajhood at fl dot net dot au, Hermann dot Rochholz at faidor dot de,gcc-bugs at gcc dot gnu dot org, karl at gnu dot org, bkoz at gcc dot gnu dot org,rkl at connect dot org dot uk, apiszcz at mitre dot org
- References: <200108242148.f7OLmBo78792@latour.rsch.comm.mot.com>
Loren James Rittle wrote:-
> ``First, we @strong{highly} recommend that GCC be built into a
> separate directory than the sources which does @strong{not} reside
> within the source tree. This is how we generally build GCC;
> building where @var{srcdir} == @var{objdir} should still work, but
> doesn't get extensive testing; building where @var{objdir} is a
> subdirectory of @var{srcdir} is unsupported.''
FWIW, if .../gcc is the base of the source tree (i.e. it contains the
MAINTAINERS file), ever since I started work on GCC 18 months ago I
have used .../gcc/build as my objdir. By my reading of the above
paragraph, I am violating the "@strong{not} reside in the source tree"
part. But it has not failed me even once. [I reported it as broken
once, but I was confused.] This layout isn't mixing up obj files with
source files, but nor is it a wholly separate part of the directory
tree.
I normally build GCC on Linux with gmake; it could well be different
for other OS / makefile combinations.
Neil.