From: Anatoly Ivanov <avi@levi.spb.ru>
To: "Kissandrakis S. George" <kissand@phaistosnetworks.gr>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.5 and gcc v3 final
Date: Wed, 20 Jun 2001 16:24:27 +0400 [thread overview]
Message-ID: <3B3095FB.2060706@levi.spb.ru> (raw)
In-Reply-To: <3B30910F.6EDCC7A1@phaistosnetworks.gr>
Hi,
Solution is simple:
change line 540 from "extern struct timeval xtime;"
to "extern volatile struct timeval xtime;"
and have fun :)
---
avi
Kissandrakis S. George wrote:
> Hello
> I suppose that you allready know it
> I have installed gcc v3 released Jun 18 and i tried to compile the
> kernel and i got
> these errors
>
> in make dep i got several warnings that look like this
>
> /usr/src/linux-2.4.5/include/asm/checksum.h:161:17: warning: multi-line
> string literals are deprecated
>
> but finally passed..
>
> in make bzImage i got
>
> timer.c:35: conflicting types for `xtime'
> /usr/src/linux-2.4.5/include/linux/sched.h:540: previous declaration of
> `xtime'
>
> and compilation stops
> if i remove the decleration of xtime in sched.h (remove the 540 line)
> the compile
> will go on and some compiles after...
>
> time.c: In function `do_normal_gettime':
> time.c:41: `xtime' undeclared (first use in this function)
>
> and some other errors
> if in time.c include the line 540 from sched.h (the xtime) the
> compilation will go on
> until the same error on another file
> i include again the line 540 from sched.h the compilation goes on etc
> etc and after lots
> of errors finally i got bzImage
>
> I didnt test bzImage if it boots
>
> with gcc v2.x the same kernel and kernel config it compiles,Is it a
> kernel bug, a gcc
> bug or something else (bad installation of gcc, my mistake etc etc)?
>
> Best Regards
>
>
> ---
> Kissandrakis S. George [kissand@phaistosnetworks.gr]
> Network and System Administrator [http://www.phaistosnetworks.gr/]
> Tel:(+30 81) 391882/Fax:(+30 892) 23206
> Phaistos Networks S.A. - A DOL Digital Company
> -
> 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:[~2001-06-20 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 12:03 2.4.5 and gcc v3 final Kissandrakis S. George
2001-06-20 12:24 ` Anatoly Ivanov [this message]
2001-06-22 1:47 ` Fabian Arias
2001-06-22 6:29 ` Anatoly Ivanov
2001-06-24 3:52 ` Anuradha Ratnaweera
2001-06-24 16:33 ` Fabian Arias
2001-06-24 17:33 ` Horst von Brand
2001-06-25 16:58 ` Anuradha Ratnaweera
2001-06-25 18:59 ` [PATCH] GCC v3 warning fixes #1 (Was: Re: 2.4.5 and gcc v3 final) Anuradha Ratnaweera
2001-06-25 22:41 ` 2.4.5 and gcc v3 final Andreas Bombe
2001-06-26 15:04 ` Anuradha Ratnaweera
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=3B3095FB.2060706@levi.spb.ru \
--to=avi@levi.spb.ru \
--cc=kissand@phaistosnetworks.gr \
--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