From: John Cherry <cherry@osdl.org>
To: root@chaos.analogic.com
Cc: Timothy Miller <miller@techsource.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Can one build 2.5.68 with allyesconfig?
Date: 23 Apr 2003 12:52:41 -0700 [thread overview]
Message-ID: <1051127561.20214.20.camel@cherrypit.pdx.osdl.net> (raw)
In-Reply-To: <Pine.LNX.4.53.0304221701320.17809@chaos>
As mentioned in other mail, compile statistics for the latest 2.5
kernels are at: http://www.osdl.org/archive/cherry/stability/
However, these statistics are based on defconfig and allmodconfig builds
(not allyesconfig). The allmodconfig build contains the riscom8 errors
that you have observed as well as most other warnings/errors you would
find in an allyesconfig build.
I have also compiled a list of cli/sti removal candidates. The files
that flag cli/save_flags conversions are:
===========================================
cli, save_flags conversions: 66 files
===========================================
drivers/atm/ambassador.c
drivers/atm/uPD98402.c
drivers/atm/zatm.c
drivers/cdrom/cdu31a.c
drivers/cdrom/cm206.c
drivers/cdrom/sbpcd.c
drivers/cdrom/sonycd535.c
drivers/char/cyclades.c
drivers/char/epca.c
drivers/char/esp.c
drivers/char/ftape/lowlevel/fdc-io.c
drivers/char/ftape/lowlevel/ftape-calibr.c
drivers/char/ftape/lowlevel/ftape-format.c
drivers/char/generic_serial.c
drivers/char/ip2main.c
drivers/char/isicom.c
drivers/char/istallion.c
drivers/char/moxa.c
drivers/char/mxser.c
drivers/char/rocket.c
drivers/char/stallion.c
drivers/i2c/i2c-elektor.c
drivers/isdn/act2000/capi.h
drivers/isdn/divert/divert_init.c
drivers/isdn/divert/divert_procfs.c
drivers/isdn/divert/isdn_divert.c
drivers/isdn/hardware/avm/b1.c
drivers/isdn/hardware/avm/c4.c
drivers/isdn/hardware/avm/t1isa.c
drivers/isdn/hysdn/boardergo.c
drivers/isdn/hysdn/hysdn_proclog.c
drivers/isdn/hysdn/hysdn_sched.c
drivers/isdn/i4l/isdn_audio.c
drivers/isdn/i4l/isdn_tty.c
drivers/isdn/i4l/isdn_ttyfax.c
drivers/isdn/icn/icn.c
drivers/isdn/isdnloop/isdnloop.c
drivers/isdn/pcbit/edss1.c
drivers/isdn/pcbit/layer2.c
drivers/isdn/sc/command.c
drivers/isdn/sc/message.c
drivers/isdn/sc/shmem.c
drivers/isdn/sc/timer.c
drivers/net/3c527.c
drivers/net/82596.c
drivers/net/hamradio/6pack.c
drivers/net/hamradio/dmascc.c
drivers/net/hamradio/mkiss.c
drivers/net/irda/toshoboe.c
drivers/net/ni5010.c
drivers/net/ni65.c
drivers/net/pcmcia/fmvj18x_cs.c
drivers/net/pcmcia/nmclan_cs.c
drivers/net/sk_mca.c
drivers/net/tulip/xircom_tulip_cb.c
drivers/net/wan/comx-hw-comx.c
drivers/net/wan/comx-hw-locomx.c
drivers/net/wan/comx-hw-mixcom.c
drivers/net/wan/comx.c
drivers/net/wan/sdla.c
drivers/net/wan/sdla_x25.c
drivers/net/wan/x25_asy.c
drivers/scsi/AM53C974.c
drivers/scsi/mca_53c9x.c
drivers/scsi/psi240i.c
fs/nfsd/nfs4proc.c
The complete list of porting items that I have pulled from compiler
output can be found at:
http://www.osdl.org/archive/cherry/stability/linus-tree/port_items.txt
Sorry about occasional 404 problems. This is an update artifact that we
are working on. Just try again.
John
On Tue, 2003-04-22 at 14:06, Richard B. Johnson wrote:
> On Tue, 22 Apr 2003, Timothy Miller wrote:
>
> > Is anyone else able to build 2.5.68 w
> ith 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
> [SNIPPED...]
>
> 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.
>
>
> Cheers,
> 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.
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2003-04-23 19:42 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
2003-04-23 19:52 ` John Cherry [this message]
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:
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=1051127561.20214.20.camel@cherrypit.pdx.osdl.net \
--to=cherry@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miller@techsource.com \
--cc=root@chaos.analogic.com \
/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).