From: Tom Tromey <tromey@redhat.com>
To: Phil Edwards <pedwards@disaster.jaj.com>
Cc: Nathanael Nerode <neroden@doctormoo.dyndns.org>, gcc@gcc.gnu.org
Subject: Re: autoconfiscating top level directory -- info wanted
Date: Thu, 03 Jan 2002 12:34:00 -0000 [thread overview]
Message-ID: <87ofkbjh7o.fsf@creche.redhat.com> (raw)
In-Reply-To: Phil Edwards's message of "Thu, 3 Jan 2002 13:59:55 -0500"
>>>>> "Phil" == Phil Edwards <pedwards@disaster.jaj.com> writes:
>> (The current script assumes a huge list of tools including emacs
>> 18, emacs 19, apache (!?!), and so I hope they aren't all still
>> configured by this script!)
Phil> I honestly don't know about some of that stuff. Obviously
Phil> they're not part of the toolchain[*], but I can see where the
Phil> original authors might have said to themselves, "hey, let's
Phil> write a super-generic build script that can configure arbitrary
Phil> programs," or some such.
The top-level configure.in code was written inside Cygnus in the
distant past. The code in the gcc and src trees still has pieces of
this legacy. For instance, I added the apache build rules in early
1996 to support a project we were working on at the time. The Emacs
stuff even predates that.
Tom
next prev parent reply other threads:[~2002-01-03 20:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 5:22 Nathanael Nerode
2002-01-03 11:13 ` DJ Delorie
[not found] ` <3C34AE17.4090701@twcny.rr.com>
2002-01-03 11:58 ` DJ Delorie
2002-01-03 11:28 ` Phil Edwards
2002-01-03 11:47 ` Zack Weinberg
2002-01-03 12:34 ` Tom Tromey [this message]
2002-01-25 14:49 Nathanael Nerode
2002-01-27 23:50 ` DJ Delorie
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=87ofkbjh7o.fsf@creche.redhat.com \
--to=tromey@redhat.com \
--cc=gcc@gcc.gnu.org \
--cc=neroden@doctormoo.dyndns.org \
--cc=pedwards@disaster.jaj.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).