From: Paul Schlie <schlie@comcast.net>
To: Andreas Schwab <schwab@suse.de>
Cc: James E Wilson <wilson@specifixinc.com>,
Nick Clifton <nickc@redhat.com>, Ben Elliston <bje@au1.ibm.com>,
<binutils@sources.redhat.com>
Subject: Re: build failure for ia64 (due to -Werror)
Date: Sun, 20 Mar 2005 09:26:00 -0000 [thread overview]
Message-ID: <BE623F8A.9880%schlie@comcast.net> (raw)
> Andreas Schwab writes:
>> James E Wilson <wilson@specifixinc.com> writes:
>>> On Fri, 2005-03-18 at 17:23, Andreas Schwab wrote:
>>> IMHO the only change we need is to check for BFD_HOST_64_BIT and error
>>> out if that is not defined.
>>
>> Doesn't that break --enable-targets=all on a 32-bit host without long
>> long?
>
> Yes, that is true. Although they are becoming rarer nowadays, and whether
> it is worth to support this combination is another question.
- Just to double check; 32-bit limited hosts would still be able to
build/support correspondingly limited targets, yes?
next reply other threads:[~2005-03-20 1:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-20 9:26 Paul Schlie [this message]
2005-03-20 19:42 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2005-03-18 3:58 Ben Elliston
2005-03-18 13:14 ` Nick Clifton
2005-03-18 14:13 ` Alan Modra
2005-03-18 22:15 ` James E Wilson
2005-03-18 22:49 ` Ian Lance Taylor
2005-03-18 23:31 ` Ian Lance Taylor
2005-03-18 23:52 ` James E Wilson
2005-03-18 23:37 ` Andreas Schwab
2005-03-19 0:42 ` Alan Modra
2005-03-19 1:56 ` Andreas Schwab
2005-03-19 4:04 ` James E Wilson
2005-03-19 4:30 ` Andreas Schwab
2005-03-19 9:44 ` James E Wilson
2005-03-19 12:13 ` James E Wilson
2005-03-19 17:57 ` James E Wilson
2005-03-19 18:37 ` Alan Modra
2005-03-19 18:33 ` James E Wilson
2005-03-19 19:00 ` Andreas Schwab
2005-03-23 9:45 ` James E Wilson
2005-03-23 19:24 ` Nick Clifton
2005-03-24 9:27 ` James E Wilson
2005-03-24 14:58 ` Nick Clifton
2005-03-19 0:56 ` Alan Modra
2005-03-22 2:19 ` Ben Elliston
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=BE623F8A.9880%schlie@comcast.net \
--to=schlie@comcast.net \
--cc=binutils@sources.redhat.com \
--cc=bje@au1.ibm.com \
--cc=nickc@redhat.com \
--cc=schwab@suse.de \
--cc=wilson@specifixinc.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).