From: Andrew Cagney <cagney@gnu.org>
To: Paul Gilliam <pgilliam@us.ibm.com>
Cc: Daniel Jacobowitz <drow@false.org>, gdb@sources.redhat.com
Subject: Re: Problem building GDB on Power64
Date: Thu, 02 Sep 2004 18:51:00 -0000 [thread overview]
Message-ID: <41376B47.70405@gnu.org> (raw)
In-Reply-To: <20040902175859.GA16559@nevyn.them.org>
>>> PS: I'm not asking for someone to post patches to configure.in or what ever,
>>> (hinting maybe), but I am asking for some pointers on where to look.
>
>
> This would be very tricky to do. GDB links to libraries built in the
> same tree, so nothing in gdb/configure.in would work. It would have to
> be in the top level, which is shared with binutils and gcc and so on.
> You don't want them to default to being 64-bit apps, because they
> should obey the system policy of defaulting to 32-bit.
>
> I really think this is your responsibility when building GDB if you
> want it to support 64-bit binaries.
Exactly.
GDB's build behavior is determined by policies set by autotools, config
and <top-level>. GDB isn't in a position to vary this locally.
Perhaphs the thing to do is rase this on GCC (where I'd guess the
<top-level> aspect should be discussed).
BTW, I did once ask to the config maintainer (BJE@ibm) if config.guess
could look at the compiler. That way, instead of:
$ CC='cc -m64' config.guess
powerpc-unknown-linux-gnu
it would return:
$ CC='cc -m64' config.guess
powerpc64-unknown-linux-gnu
and that in turn would let us specify:
$ CC='cc -m64' .../configure
Ben didn't agree (I don't remember why).
Andrew
next prev parent reply other threads:[~2004-09-02 18:51 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 [this message]
2004-09-02 20:17 ` Michael Chastain
2004-09-02 20:30 ` Eli Zaretskii
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=41376B47.70405@gnu.org \
--to=cagney@gnu.org \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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