[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Compiling the kernel with the new gcc - help



I recently compiled the 2.2.12 kernel and noticed that the no-strict-alias is
added by default with the latest gcc versions.  No problems.  2.2.10 is
outdated, so why not upgrade?

							Dave Bristel


On Fri, 3 Sep 1999, Juli-Manel Merino Vidal wrote:

> Date: Fri, 3 Sep 1999 17:44:22 +0200 (CEST)
> From: Juli-Manel Merino Vidal <jmmv@mail.com>
> To: Gordon Russell <gor@dcs.napier.ac.uk>
> Cc: Debian Developers <debian-devel@lists.debian.org>
> Subject: Re: Compiling the kernel with the new gcc - help
> Resent-Date: 3 Sep 1999 15:42:10 -0000
> Resent-From: debian-devel@lists.debian.org
> Resent-cc: recipient list not shown: ;
> 
> On Fri, 3 Sep 1999, Gordon Russell wrote:
> 
> > 
> > I have compiled the kernel many times in the past, but now I am really stuck...
> > 
> > I am getting messages like:
> > 
> > seagate.c: In function `internal_command':
> > seagate.c:1252: Invalid `asm' statement:
> > seagate.c:1252: fixed or forbidden register 3 (bx) was spilled for class BREG.
> > 
> > I am using kernel 2.2.10, and the new gcc 2.95-1.
> > I changed the CFLAGS to have -fno-strict-aliasing, as advised in the README.
> 
> I've compiled 2.2.12 with that gcc and WITHOUT adding that option and
> works fine.
> 
> > 
> > Any thoughts?
> > G.
> > 
> > -- 
> > Gordon Russell
> > http://www.dcs.napier.ac.uk/~gor
> > PGP Public Key - http://www.dcs.napier.ac.uk/~gor/pgpkey.txt
> > 
> > 
> > -- 
> > To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> > with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> > 
> > 
> 
> ----------------------------------------
> Juli-Manel Merino Vidal
> jmmv@mail.com - http://jmmv.cjb.net
> ----------------------------------------
>         >>> Running Debian/GNU Linux 2.1
> 
> 
> 
> -- 
> To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
> with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
> 


Reply to: