From: William Lee Irwin III <wli@holomorphy.com>
To: sparclinux@vger.kernel.org
Subject: Re: Sun4d progress
Date: Thu, 19 Aug 2004 14:12:25 +0000 [thread overview]
Message-ID: <20040819141225.GN11200@holomorphy.com> (raw)
In-Reply-To: <Pine.LNX.4.53.0408182135050.391@mailgate.netunix.com>
On Wed, Aug 18, 2004 at 10:57:47PM +0100, C.Newport wrote:
>> Something odd is going on - Thomas claimed that 2.4.23-pre5 booted but
>> was unstable, which I cannot achieve. Maybe our environments are
>> different, but I have built this 4 times with 2.4.22 and 2.4.27 on both
>> old and new compilers and the result is consistent. Maybe Thomas had
>> applied some other patch before these ?.
On Thu, Aug 19, 2004 at 02:47:17PM +0200, Thomas Bogendoerfer wrote:
> hmm, thinking about it, there is one hunk I usually throw out of that
> patch:
[...]
> Without that gcc 3.0.4 generates instructions, which btfixup couldn't
> resolve. I suspect there are some compiler troubles left, because the
> images I've build with gcc 3.3.3 aren't even working on my SS20 last
> time I tried ...
Okay, what gcc/binutils is everyone using and can we start slinging
binaries compiled from the same kernel compiled by different gcc's
around so I can diagnose this? Thanks.
-- wli
next prev parent reply other threads:[~2004-08-19 14:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-18 21:28 Sun4d progress Chris Newport
2004-08-18 21:33 ` William Lee Irwin III
2004-08-18 21:39 ` Keith M Wesolowski
2004-08-18 21:41 ` William Lee Irwin III
2004-08-18 21:57 ` C.Newport
2004-08-18 22:00 ` William Lee Irwin III
2004-08-19 12:47 ` Thomas Bogendoerfer
2004-08-19 14:12 ` William Lee Irwin III [this message]
2004-08-19 14:28 ` Meelis Roos
2004-08-19 16:18 ` Keith M Wesolowski
2004-08-19 17:12 ` C.Newport
2004-08-19 17:16 ` William Lee Irwin III
2004-08-19 17:53 ` C.Newport
2004-08-19 17:56 ` William Lee Irwin III
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=20040819141225.GN11200@holomorphy.com \
--to=wli@holomorphy.com \
--cc=sparclinux@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.