archive mirror
 help / color / mirror / Atom feed
From: "Richard B. Johnson" <>
To: Timothy Miller <>
Cc: Linux Kernel Mailing List <>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: Tue, 22 Apr 2003 17:06:29 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.53.0304221701320.17809@chaos> (raw)
In-Reply-To: <>

On Tue, 22 Apr 2003, Timothy Miller wrote:

> Is anyone else able to build 2.5.68 with allyesconfig?
> I'm using RH7.2, so the first thing I did was edit the main Makefile to
> replace gcc with "gcc3" (3.0.4).  Maybe the compiler is STILL my
> problem.  The problem doesn't stand out clearly to me, but I also
> haven't put much thought into it.  I'll try to use some more of my
> brain.  But if it's not going to be fixable by me, I humbly request help.
> Before the compile terminates, there are a number of the same warning
> for other files, being the same as the ones below for 'flags'.
> The compile dies thusly:
>   gcc3 -Wp,-MD,drivers/char/.riscom8.o.d -D__KERNEL__ -Iinclude -Wall
> -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=i686
> -Iinclude/asm-i386/mach-default -nostdinc -iwithprefix include
> -DKBUILD_BASENAME=riscom8 -DKBUILD_MODNAME=riscom8 -c -o
> drivers/char/.tmp_riscom8.o drivers/char/riscom8.c

drivers/char/riscom8.c uses old methods including 'cli' and 'sti'.
It hasn't been fixed yet. Remove this from your configuration
and try again.

No code should use cli and sti. If any compile errors out on 2.5.n.n,
as a result of this, and you need the driver, you might try to inspect
the source and contact its maintainer. There are a lot of cleanups
on-going in this version.

Dick Johnson
Penguin : Linux version 2.4.20 on an i686 machine (797.90 BogoMips).
Why is the government concerned about the lunatic fringe? Think about it.

  parent reply	other threads:[~2003-04-22 20:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-22 20:49 Can one build 2.5.68 with allyesconfig? Timothy Miller
2003-04-22 20:41 ` Valdis.Kletnieks
2003-04-22 20:51   ` Randy.Dunlap
2003-04-22 21:04   ` Timothy Miller
2003-04-22 20:57     ` Valdis.Kletnieks
2003-04-22 22:25       ` Timothy Miller
2003-04-22 21:06 ` Richard B. Johnson [this message]
2003-04-23 19:52   ` John Cherry
2003-04-23 20:48     ` Jörn Engel
2003-04-24  0:01       ` John Cherry
2003-04-24  9:26         ` Jörn Engel
2003-04-22 21:08 ` Sam Ravnborg
2003-04-22 21:19   ` Randy.Dunlap
2003-04-23 11:58 ` Jörn Engel

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.53.0304221701320.17809@chaos \ \ \ \

* 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).