From: Oleg Drokin <green@namesys.com>
To: Ivan Kokshaysky <ink@jurassic.park.msu.ru>
Cc: "T. Weyergraf" <kirk@colinet.de>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.73 on alpha/smp build failure
Date: Mon, 30 Jun 2003 15:05:00 +0400 [thread overview]
Message-ID: <20030630110500.GA29672@namesys.com> (raw)
In-Reply-To: <20030630145243.A22506@jurassic.park.msu.ru>
Hello!
On Mon, Jun 30, 2003 at 02:52:43PM +0400, Ivan Kokshaysky wrote:
> > See attached assembly generated by cross compiler vs native compiler.
> Code generated by gcc-2.95 is obviously bogus. Which is not surprising -
> 2.95 is known to be broken for 32-bit host -> 64-bit target
> cross-compilation. Try something more recent. ;-)
Sigh. So I suddenly succeed in building cross gcc-3.3 that works correctly with
my simple test (for some reason it needed to disable dynamic libgcc build
before I was able to get at least something working). And now guess what?
I get "bad kernel unaligned access ..." message at the point where sda's partition
table would get normally printed. The first address printed is somewhere near end of
__make_request, the second address is prior to the kernel start, and two last numbers are
"22 31".
If I disable SCSI completely, it even boots and works which is of course a great
progress over what I had with gcc-2.95 (it boots off IDE anyway). ;)
I will try to get newer binutils on the box itself to see if it will make any
difference for the kernel built natively.
Bye,
Oleg
next prev parent reply other threads:[~2003-06-30 10:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-28 9:28 2.5.73 on alpha/smp build failure T. Weyergraf
2003-06-28 13:38 ` Oleg Drokin
2003-06-29 11:56 ` Ivan Kokshaysky
2003-06-30 5:42 ` Oleg Drokin
2003-06-30 10:52 ` Ivan Kokshaysky
2003-06-30 11:05 ` Oleg Drokin [this message]
2003-06-29 11:45 ` Ivan Kokshaysky
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=20030630110500.GA29672@namesys.com \
--to=green@namesys.com \
--cc=ink@jurassic.park.msu.ru \
--cc=kirk@colinet.de \
--cc=linux-kernel@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 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 NNTP newsgroup(s).