From: mike stump <mrs@windriver.com>
To: mark@codesourcery.com, per@bothner.com
Cc: gcc@gcc.gnu.org
Subject: Re: Installation proposal
Date: Thu, 28 Feb 2002 11:51:00 -0000 [thread overview]
Message-ID: <200202281940.LAA03761@kankakee.wrs.com> (raw)
> Date: Thu, 28 Feb 2002 09:04:06 -0800
> From: Per Bothner <per@bothner.com>
> To: Mark Mitchell <mark@codesourcery.com>
> CC: "gcc@gcc.gnu.org" <gcc@gcc.gnu.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
methodology?
next reply other threads:[~2002-02-28 19:40 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-28 11:51 mike stump [this message]
2002-02-28 12:56 ` Mark Mitchell
2002-02-28 14:04 ` Alexandre Oliva
2002-02-28 14:28 ` Per Bothner
2002-02-28 16:32 ` Richard Henderson
2002-02-28 17:19 ` rpath editors (was Re: Installation proposal) Zack Weinberg
-- strict thread matches above, loose matches on Subject: below --
2002-02-27 13:22 Installation proposal mike stump
2002-02-27 11:07 Benjamin Kosnik
2002-02-27 10:48 Mark Mitchell
2002-02-27 10:11 Mark Mitchell
2002-02-27 10:25 ` H . J . Lu
2002-02-27 10:26 ` David Edelsohn
2002-02-27 10:59 ` Jim Wilson
2002-02-27 13:05 ` Michael Meissner
2002-02-27 10:50 ` Paul Koning
2002-02-27 11:02 ` Stan Shebs
2002-02-27 11:04 ` Joseph S. Myers
2002-02-27 11:25 ` Mark Mitchell
2002-02-27 12:10 ` Joseph S. Myers
2002-02-27 11:05 ` Joel Sherrill
2002-02-27 11:53 ` Joseph S. Myers
2002-02-27 11:07 ` Tom Tromey
2002-02-27 11:26 ` Mark Mitchell
2002-02-27 14:55 ` Richard Henderson
2002-02-27 17:38 ` Alexandre Oliva
2002-02-27 17:45 ` Richard Henderson
2002-02-27 18:27 ` Alexandre Oliva
2002-02-28 0:04 ` Richard Henderson
2002-02-28 2:02 ` Joseph S. Myers
2002-02-28 2:25 ` Alexandre Oliva
2002-02-27 11:13 ` Laurent Guerby
2002-02-27 12:11 ` Zack Weinberg
2002-02-27 12:17 ` Jim Wilson
2002-02-27 14:43 ` Laurent Guerby
2002-02-27 12:52 ` Neil Booth
2002-02-27 11:18 ` Jim Wilson
2002-02-27 14:56 ` Daniel Jacobowitz
2002-02-27 17:18 ` Mark Mitchell
2002-02-27 17:20 ` Richard Henderson
2002-02-27 17:59 ` Mark Mitchell
[not found] ` <mailpost.1014859095.10690@news-sj1-1>
2002-02-27 18:16 ` cgd
2002-02-27 11:23 ` Per Bothner
2002-02-28 1:39 ` Akim Demaille
2002-02-27 14:56 ` Nathan Sidwell
2002-02-27 16:11 ` Loren James Rittle
2002-02-27 17:47 ` Alexandre Oliva
2002-02-27 18:00 ` Daniel Jacobowitz
2002-02-28 14:06 ` Alexandre Oliva
2002-02-27 18:33 ` Mark Mitchell
2002-02-28 9:18 ` Per Bothner
2002-02-28 9:42 ` Mark Mitchell
2002-02-28 1:13 ` Akim Demaille
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200202281940.LAA03761@kankakee.wrs.com \
--to=mrs@windriver.com \
--cc=gcc@gcc.gnu.org \
--cc=mark@codesourcery.com \
--cc=per@bothner.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).