From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: hjl@lucon.org (H.J. Lu), jgotts@engin.umich.edu, egcs@cygnus.com
Subject: Re: libf2c problem
Date: Mon, 09 Feb 1998 23:36:00 -0000 [thread overview]
Message-ID: <13588.887089637@hurl.cygnus.com> (raw)
In-Reply-To: <199802100014.QAA19278@atrus.synopsys.com>
In message < 199802100014.QAA19278@atrus.synopsys.com >you write:
> It seems that dejagnu is too tightly coupled to the Cygnus tree structure
> and has too much builtin knowledge of How Things Are Supposed To Be,
> so it is very brittle. Is there any way that this can be addressed?
> It seems that paths to libraries should be part of the egcs distribution
> and not dejagnu.
Hard to argue with that statement... The dejagnu situation is far
from ideal.
I don't have any good technical ideas on how to implement this
though.
jeff
next prev parent reply other threads:[~1998-02-09 23:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <199802090739.CAA23597@pa.engin.umich.edu>
1998-02-09 14:46 ` H.J. Lu
1998-02-09 19:49 ` Joe Buck
1998-02-09 21:34 ` John Gotts
1998-02-10 3:34 ` Jeffrey A Law
1998-02-10 14:45 ` Mark Mitchell
1998-02-09 23:36 ` Jeffrey A Law [this message]
1998-02-10 12:11 Mike Stump
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=13588.887089637@hurl.cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=hjl@lucon.org \
--cc=jbuck@synopsys.com \
--cc=jgotts@engin.umich.edu \
/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).