From: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
To: egcs@cygnus.com
Cc: Craig Burley <burley@gnu.org>,
sichen@studbox.uni-stuttgart.de, law@cygnus.com
Subject: Re: egcs-1.0.2 installation
Date: Sun, 19 Apr 1998 01:49:00 -0000 [thread overview]
Message-ID: <Pine.NEB.3.96.980419103306.25736C-100000@elnath.dbai.tuwien.ac.at> (raw)
In-Reply-To: <12592.892876203@hurl.cygnus.com>
On Fri, 17 Apr 1998, Jeffrey A Law wrote:
> * For years folks have been striving to make the gnu tools easier
> to build/install and have been preacing the "tar xzf blah.tar.gz; cd blah;
> configure; make" as all they need to do for most installations.
I agree that this should work, if possible in any way.
What originally triggered this thread, however, was the case where someone
would build in a separate tree which is rooted within the source tree.
_This_ we should warn against and, as someone else has suggested, we could
even detect and refuse to build in such a situation.
Gerald
--
Gerald Pfeifer (Jerry) Vienna University of Technology
pfeifer@dbai.tuwien.ac.at http://www.dbai.tuwien.ac.at/~pfeifer/
next prev parent reply other threads:[~1998-04-19 1:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-04-15 2:25 Markus Sicheneder
1998-04-15 11:37 ` Jeffrey A Law
1998-04-15 15:09 ` Markus Sicheneder
1998-04-15 19:57 ` Jeffrey A Law
1998-04-16 13:53 ` egcs-1.0.2 installation (still problems) Markus Sicheneder
1998-04-15 23:03 ` egcs-1.0.2 installation Gerald Pfeifer
1998-04-16 10:51 ` Craig Burley
1998-04-18 1:43 ` Jeffrey A Law
1998-04-17 23:53 ` Craig Burley
1998-04-19 1:49 ` Gerald Pfeifer [this message]
1998-05-07 6:52 ` PATCH: htdocs/install/configure.html Gerald Pfeifer
1998-05-08 13:02 ` Jeffrey A Law
1998-04-16 2:26 ` egcs-1.0.2 installation Manfred Hollstein US/EPB3 60/1F/110 #40283
1998-04-16 10:51 ` Horst von Brand
1998-04-16 18:39 ` Markus Sicheneder
1998-04-17 22:05 ` Jeffrey A Law
-- strict thread matches above, loose matches on Subject: below --
1998-04-07 15:26 Bart Vansegbroeck
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=Pine.NEB.3.96.980419103306.25736C-100000@elnath.dbai.tuwien.ac.at \
--to=pfeifer@dbai.tuwien.ac.at \
--cc=burley@gnu.org \
--cc=egcs@cygnus.com \
--cc=law@cygnus.com \
--cc=sichen@studbox.uni-stuttgart.de \
/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).