public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jochen Striepe <jochen@tolot.escape.de>
To: Alan Cox <laughing@shared-source.org>, linux-kernel@vger.kernel.org
Subject: Re: Linux 2.2.20-pre4
Date: Tue, 19 Jun 2001 17:22:19 +0200	[thread overview]
Message-ID: <20010619172219.A18744@tolot.escape.de> (raw)
In-Reply-To: <20010619152912.A23175@lightning.swansea.linux.org.uk>
In-Reply-To: <20010619152912.A23175@lightning.swansea.linux.org.uk>

        Hi,

On 19 Jun 2001, Alan Cox <laughing@shared-source.org> wrote:
> 
> 2.2.20pre4

Just to keep you informed... (I think there was a saying that there was
interest in experiences with compiling the kernel with non-recommended
gcc's ...)

I tried the newly released gcc-3.0 compiling 2.2.20pre4 (yes, I _know_ it
is not recommended): 

/usr/src/linux/include/linux/signal.h: In function `siginitset':
/usr/src/linux/include/linux/signal.h:193: warning: deprecated use of label at end of compound statement
/usr/src/linux/include/linux/signal.h: In function `siginitsetinv':
/usr/src/linux/include/linux/signal.h:205: warning: deprecated use of label at end of compound statement
sched.c: At top level:
sched.c:52: conflicting types for `xtime'
/usr/src/linux/include/linux/sched.h:509: previous declaration of `xtime'
sched.c: In function `schedule':
sched.c:739: warning: deprecated use of label at end of compound statement
make[2]: *** [sched.o] Error 1
make[2]: Leaving directory `/usr/src/linux-2.2.20pre4/kernel'
make[1]: *** [first_rule] Error 2
make[1]: Leaving directory `/usr/src/linux-2.2.20pre4/kernel'
make: *** [_dir_kernel] Error 2


$ sh /usr/src/linux/scripts/ver_linux 
If some fields are empty or look unusual you may have an old version.
Compare to the current minimal requirements in Documentation/Changes.
 
Linux tolot 2.4.6-pre3 #1 Wed Jun 13 09:55:57 CEST 2001 i586 unknown
 
Gnu C                  3.0
Gnu make               3.79.1
binutils               2.11.1
util-linux             2.11f
mount                  2.11f
modutils               2.4.6
e2fsprogs              1.21
PPP                    2.4.1
Linux C Library        2.2.3
Dynamic linker (ldd)   2.2.3
Procps                 2.0.7
Net-tools              1.60
Kbd                    1.06
Sh-utils               2.0.11
Modules Loaded         nls_utf8 nls_iso8859-15 nls_iso8859-2
nls_iso8859-1 nls_cp852 nls_cp850 nls_cp437 floppy sr_mod sg isofs
ne2k-pci 8390 ide-cd cdrom adlib_card opl3 sb sb_lib uart401 sound
soundcore ppp_generic slhc lp parport serial


So long,

Jochen.

-- 
Cahn's Axiom:
        When all else fails, read the instructions.

  reply	other threads:[~2001-06-19 15:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-19 14:29 Linux 2.2.20-pre4 Alan Cox
2001-06-19 15:22 ` Jochen Striepe [this message]
2001-06-19 15:23   ` Alan Cox
2001-06-19 16:26     ` Jochen Striepe
2001-06-19 16:42       ` Jochen Striepe
2001-06-19 20:03 ` Tomasz Kłoczko
2001-06-19 20:22   ` Alan Cox
2001-06-19 21:48     ` Jeff Garzik
2001-06-19 21:57       ` Alan Cox
2001-06-19 22:16         ` Jeff Garzik
2001-06-19 22:03       ` Philip Blundell
2001-06-19 22:18         ` Jeff Garzik
2001-06-20 21:23     ` Eric Lammerts
2001-06-21  8:43       ` Luigi Genoni

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=20010619172219.A18744@tolot.escape.de \
    --to=jochen@tolot.escape.de \
    --cc=laughing@shared-source.org \
    --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