From: Jeffrey A Law <law@cygnus.com>
To: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
Cc: egcs@cygnus.com
Subject: Re: Install instructions + dejagnu suggestion
Date: Mon, 01 Dec 1997 07:38:00 -0000 [thread overview]
Message-ID: <10126.880986687@hurl.cygnus.com> (raw)
In-Reply-To: <Pine.LNX.3.96.971201093807.17181A-100000@argon.roma2.infn.it>
In message < Pine.LNX.3.96.971201093807.17181A-100000@argon.roma2.infn.it >you
write:
> Now, at first the egcs thing: I think the instructions should contain some
> hint to the
> --program-prefix
> configure option, which could be useful to those who would like to have
> both GNU gcc and egcs available (and was noted in some message in the
> mailing list).
We're recommending using --prefix and a few symlinks. It avoids problems
with g++ header file conflicts. See the faq.
> Then, even though I'm not sure it belongs here, the dejagnu
> question/suggestion: in as much as I can see, deja runs at all from expect
> scripts. Shouldn't then be possible to do some tests to see if expect and
> tcl/tk have been installed on the system before the build? This comes from
> bad results I got from a make check inside dejagnu build directory in a
> debian system where I had both tcl/tk installed, but unrecognized... I
> mean: trying to call tclsh and expect (or which tclsh, expect) could let
> the install run without recompiling both interpreters.
This is outside the scope of egcs -- we really don't want to any more time in
burn time in dejagnu than is absolutely necessary.
You might take this up with the dejagnu folks though.... dejagnu@cygnus.com
jeff
next prev parent reply other threads:[~1997-12-01 7:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 1:28 Lorenzo M. Catucci
1997-12-01 7:38 ` Jeffrey A Law [this message]
1997-12-01 7:38 ` Lorenzo M. Catucci
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=10126.880986687@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=lorenzo@argon.roma2.infn.it \
/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).