From: "Eli Zaretskii" <eliz@gnu.org>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: pgilliam@us.ibm.com, cagney@gnu.org, gdb@sources.redhat.com,
drow@false.org
Subject: Re: Problem building GDB on Power64
Date: Thu, 02 Sep 2004 20:30:00 -0000 [thread overview]
Message-ID: <01c4912b$Blat.v2.2.2$b16abc40@zahav.net.il> (raw)
In-Reply-To: <41377FBA.nail7AG11C5P9@mindspring.com> (message from Michael Chastain on Thu, 02 Sep 2004 16:16:58 -0400)
> Date: Thu, 02 Sep 2004 16:16:58 -0400
> From: Michael Chastain <mec.gnu@mindspring.com>
> Cc: gdb@sources.redhat.com, drow@false.org
>
> Here's an idea from gcc:
>
> gcc has a directory named INSTALL with a file 'specific.html', which has
> info organized by target. If we had a file like that, then that would
> be the natural place for describing build choices like -m32 and -m64.
>
> It would also be a good place for the section of PROBLEMS that
> are about build failures and their workarounds.
I think PROBLEMS is the wrong place for this, unless there's a small
number of platforms with specific build problems.
Why not put this in the INSTALL file? That's where installation
instructions belong, IMHO.
prev parent reply other threads:[~2004-09-02 20:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-02 16:23 Paul Gilliam
2004-09-02 17:22 ` Daniel Jacobowitz
2004-09-02 17:54 ` Paul Gilliam
2004-09-02 17:59 ` Daniel Jacobowitz
2004-09-02 18:51 ` Andrew Cagney
2004-09-02 20:17 ` Michael Chastain
2004-09-02 20:30 ` Eli Zaretskii [this message]
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='01c4912b$Blat.v2.2.2$b16abc40@zahav.net.il' \
--to=eliz@gnu.org \
--cc=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.com \
--cc=mec.gnu@mindspring.com \
--cc=pgilliam@us.ibm.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