From: Jeffrey A Law <law@cygnus.com>
To: Joe Buck <jbuck@synopsys.com>
Cc: pfeifer@dbai.tuwien.ac.at, egcs@cygnus.com
Subject: Re: egrep -i haifa INSTALL install.texi
Date: Mon, 01 Dec 1997 11:33:00 -0000 [thread overview]
Message-ID: <29916.881004265@cygnus.com> (raw)
In-Reply-To: <199712011803.KAA26566@atrus.synopsys.com>
In message < 199712011803.KAA26566@atrus.synopsys.com >you write:
>
> > gcc/INSTALL is basically out of date and depreciated for egcs.
>
> OK. I hope you've planned one snapshot for a debugging pass on the
> included documentation (that is, it's a bad idea to do a release with
> documentation that people haven't yet seen).
Yup, it should start spinning in the next hour or so as I go back and
start tweaking the docs included in the release.
It'll also include a small number of critical fixes.
> I've always built egcs with srcdir = objdir and have not had problems.
> Is that warning appropriate? objdir is certainly appropriate for the
> system administrator who supports multiple Unix flavors, but why do
> suspect that srcdir == objdir is risky.
We've had trouble with it in the past -- multilibs haven't played well when
srcdir == objdir for example.
> I recommend that all defaults for options switches be listed;
> --with-local-prefix, --with-gxx-include-dir are missing theirs.
Thanks. Done.
> --with-newlib is not documented; a sentence saying what newlib is would
> be helpful.
Done.
> Please document bootstrap-lean:
Thanks. I used your text.
> The "make cross" directions are insufficient: the user also must obtain
> target tools and libraries -- a pointer to the crossgcc FAQ might be
> helpful here, even if it is somewhat out of date.
Hmmm, I thought I had the link. I'll go figure out what happened :-)
I suspect they will stay insufficient for a while until we get a better
handle on how to document all the pieces that folks need to build useable
cross tools.
> test.html:
>
> I suggest putting in the full path to the dejagnu testsuite as visible
> text, not just a link, so people printing out the directions have it.
Sounds reasonable. Done.
> finalinstall.html:
>
> ... where <I>prefix</I> is the value you specified with the --prefix option
> to
> configure (or /usr/local by default).
Thanks.
jeff
next prev parent reply other threads:[~1997-12-01 11:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-11-29 13:40 Gerald Pfeifer
1997-11-30 18:55 ` Jeffrey A Law
1997-12-01 11:32 ` Joe Buck
1997-12-01 11:33 ` Jeffrey A Law [this message]
1997-12-02 16:29 ` Gerald Pfeifer
1997-12-02 18:18 ` Jeffrey A Law
1997-12-02 23:24 ` H.J. Lu
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=29916.881004265@cygnus.com \
--to=law@cygnus.com \
--cc=egcs@cygnus.com \
--cc=jbuck@synopsys.com \
--cc=pfeifer@dbai.tuwien.ac.at \
/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).