From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Randolph Chung <randolph@tausq.org>
Cc: John David Anglin <dave@hiauly1.hia.nrc.ca>,
bzeeb-lists@lists.zabbadoz.net,
parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] [2.5] next issues ...
Date: Fri, 15 Nov 2002 15:50:28 -0500 [thread overview]
Message-ID: <20021115205028.GI7587@systemhalted> (raw)
In-Reply-To: <20021115192110.GE21266@tausq.org>
> > My impression from what Joel has said is that the problem is bad coding
> > rather than an actual gcc problem. However, up to now, nobody has been
> > able to provide a precise analysis of what's going on.
>
> or even duplicate the problem.. i've been building 2.4 and 2.5 kernels
> with 3.2 for some time.... haven't seen the problems that have been
> reported.
>
32 or 64-bit kernels? All debian tools? Mix of debian and upstream?
My only run-in with the problem was with 32-bit kernels cross compiled
from x86. Though lately I'm using a gcc-3.1 based XC and it builds functional
64-bit kernels.
This is definately becoming one of those HPPA urban legends. I shall add
it to my TODO list and verify that I can build a 32/64-bit kernel
natively and cross with all the latest upstream cvs bits.
c.
next prev parent reply other threads:[~2002-11-15 20:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-15 17:12 [parisc-linux] [2.5] next issues Bjoern A. Zeeb
2002-11-15 17:50 ` Carlos O'Donell
2002-11-15 19:10 ` John David Anglin
2002-11-15 19:21 ` Randolph Chung
2002-11-15 20:50 ` Carlos O'Donell [this message]
2002-11-18 13:34 ` jsoe0708
2002-11-15 22:17 ` Bjoern A. Zeeb
2002-11-15 22:45 ` John David Anglin
2002-11-15 23:29 ` Randolph Chung
2002-11-16 0:37 ` John David Anglin
2002-11-17 2:32 ` M. Grabert
2002-11-17 13:16 ` Bjoern A. Zeeb
2002-11-17 21:14 ` John David Anglin
2002-11-17 17:34 ` Bjoern A. Zeeb
2002-11-17 20:48 ` John David Anglin
2002-11-17 21:13 ` Bjoern A. Zeeb
2002-11-17 21:26 ` John David Anglin
2002-11-18 21:38 ` Bjoern A. Zeeb
2002-11-18 21:52 ` John David Anglin
2002-11-18 22:15 ` Bjoern A. Zeeb
2002-11-18 22:21 ` John David Anglin
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=20021115205028.GI7587@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=bzeeb-lists@lists.zabbadoz.net \
--cc=dave@hiauly1.hia.nrc.ca \
--cc=parisc-linux@lists.parisc-linux.org \
--cc=randolph@tausq.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