PATCH: Document the supported configuration style of gcc 3.1 and beyond

Loren James Rittle rittle@latour.rsch.comm.mot.com
Wed Apr 3 02:56:00 GMT 2002


In article <20020403054624.E1213@devserv.devel.redhat.com>,
Jakub Jelinek <jakub@redhat.com> writes:

> Strange that I use build dir as sibling of gcc,libstdc++-v3 etc. dirs
> (ie. subdirectory of the main srcdir) all the time on all targets I build on
> and never ever encountered a problem related to this...

Not strange.  That is not what we call in-source configuration...

Here is in-source configuration:

tar xvf gcc-3.1.tar   
cd gcc-3.1
./configure
make bootstrap

You will readily see why gcc developers don't do this; it pollutes our
CVS source trees.  Users that unpack gcc releases from tar files still
expect to be able to do the above.  We current document that the above
sequence "should work"; yet it doesn't currently work.  If you would
like to refine my proposed words to include how you personally
configure gcc; then be my guest.  The point is to tell end-users how
we want them to configure GCC and quite being so wishy-washy about it.

Regards,
Loren



More information about the Gcc-patches mailing list