From: Christian Joensson <christian.joensson@gmail.com>
To: binutils@sources.redhat.com
Subject: Re: FAIL: bootstrap with --static: on sparc-linux with binutils 20050222 cvs trunk
Date: Wed, 23 Feb 2005 16:42:00 -0000 [thread overview]
Message-ID: <5460e3330502230626c592eb3@mail.gmail.com> (raw)
In-Reply-To: <200502231039.28554.ebotcazou@libertysurf.fr>
On Wed, 23 Feb 2005 10:40:44 +0100, Eric Botcazou
<ebotcazou@libertysurf.fr> wrote:
> > ok, thanks. I recompiled and tested again, nothing there, so, mishap I
> > guess.
>
> Recompiled with the same 4.0.0pre compiler? Even more worrying I'd say!
well, neither was using gcc4... just some mishappening I can't
understand... clueless, however, not gcc4...
--
Cheers,
/ChJ
prev parent reply other threads:[~2005-02-23 14:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-23 10:30 Christian Joensson
2005-02-23 11:17 ` Alan Modra
2005-02-23 11:44 ` Christian Joensson
2005-02-23 12:25 ` Eric Botcazou
2005-02-23 16:42 ` Christian Joensson [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=5460e3330502230626c592eb3@mail.gmail.com \
--to=christian.joensson@gmail.com \
--cc=binutils@sources.redhat.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).