From: "Lorenzo M. Catucci" <lorenzo@argon.roma2.infn.it>
To: egcs@cygnus.com
Subject: Install instructions + dejagnu suggestion
Date: Mon, 01 Dec 1997 01:28:00 -0000 [thread overview]
Message-ID: <Pine.LNX.3.96.971201093807.17181A-100000@argon.roma2.infn.it> (raw)
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).
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.
Yours,
l.
next reply other threads:[~1997-12-01 1:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-12-01 1:28 Lorenzo M. Catucci [this message]
1997-12-01 7:38 ` Jeffrey A Law
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=Pine.LNX.3.96.971201093807.17181A-100000@argon.roma2.infn.it \
--to=lorenzo@argon.roma2.infn.it \
--cc=egcs@cygnus.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).