This is the mail archive of the
mailing list for the GCC project.
Re: Installation proposal
- From: mike stump <mrs at windriver dot com>
- To: mark at codesourcery dot com, per at bothner dot com
- Cc: gcc at gcc dot gnu dot org
- Date: Thu, 28 Feb 2002 11:40:05 -0800 (PST)
- Subject: Re: Installation proposal
> Date: Thu, 28 Feb 2002 09:04:06 -0800
> From: Per Bothner <email@example.com>
> To: Mark Mitchell <firstname.lastname@example.org>
> CC: "email@example.com" <firstname.lastname@example.org>
> My suggestion:
> (1) configure creates a 'build' sub-directory at the top-level,
> parallel to 'gcc', libstdc++', etc. The Makefiles call this
> directory $build_prefix.
I like this approach. One can do as small a job as they want, and it
will be self-consistent. A multitude of people can work in parallel.
The semantics of make all and make install are clear and unchanged.
One can start this at any level and do as much or as little a job as
they care to. The risk of this approach is lower, and the end result
I think it the same or superior. Do the objections against the
original apply to this methodology? Any new objections against this