gcc-4.1.1 and kernel-2.4.32

gcc-4.1.1 and kernel-2.4.32

[Herbert Rosmanith]

good day,

trying to compile 2.4.32 with gcc-4.1.1 (probably any 4.x gcc?) produces
a lot of errors, (i.e., declaration of symbols of different types and so on).

I wonder if it is planned to be fixed? No idea who's maintaining it - 
in case you want to, I could send you diffs to make 2.4.32 compile.

kind regards,
h.rosmanith

Re: gcc-4.1.1 and kernel-2.4.32

[Herbert Rosmanith]

> 
> good day,
> 
> trying to compile 2.4.32 with gcc-4.1.1 (probably any 4.x gcc?) produces
> a lot of errors, (i.e., declaration of symbols of different types and so on).

oh, hm .. "a lot" is a bit extreme ... 3 errors so far ;-)
 
kind regards,
h.rosmanith

Re: gcc-4.1.1 and kernel-2.4.32

[Michal Piotrowski]

Hi,

On 21/06/06, Herbert Rosmanith <kernel@wildsau.enemy.org> wrote:
> >
> > good day,
> >
> > trying to compile 2.4.32 with gcc-4.1.1 (probably any 4.x gcc?) produces
> > a lot of errors, (i.e., declaration of symbols of different types and so on).
>
> oh, hm .. "a lot" is a bit extreme ... 3 errors so far ;-)

Here are patches that fix compilation on 2.4
http://user.it.uu.se/~mikpe/linux/patches/2.4/

>
> kind regards,
> h.rosmanith
>

Regards,
Michal

-- 
Michal K. K. Piotrowski
LTG - Linux Testers Group
(http://www.stardust.webpages.pl/ltg/wiki/)

Re: gcc-4.1.1 and kernel-2.4.32

[Jan Engelhardt]

>good day,
>
>trying to compile 2.4.32 with gcc-4.1.1 (probably any 4.x gcc?) produces
>a lot of errors, (i.e., declaration of symbols of different types and so on).
>
>I wonder if it is planned to be fixed? No idea who's maintaining it - 
>in case you want to, I could send you diffs to make 2.4.32 compile.
>
In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same 
reason; called deep maintenance. 2.6 has been on the road since Dec 2003, 
that's over 2 years. Do away with the old stuff.


Jan Engelhardt
-- 

Re: gcc-4.1.1 and kernel-2.4.32

[Herbert Rosmanith]

> In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same 
> reason; called deep maintenance. 2.6 has been on the road since Dec 2003, 
> that's over 2 years. Do away with the old stuff.

we are in the process of switching, which is not unproblematic. on
the other hand, we have to support existing installations as well.

by the way ... "switching is not unproblematic": I just had to examine
a notebook which had problems with our software: a
"toshiba portege m400". 2.4 seems to work so far, as does 2.6.16.
I also tried 2.6.17, but get a strange problem: it simply hangs
after writing "PCI: probing hardware" (or similar). A closer look
reveals that it hangs in drivers/pci/probe.c, in pci_read_bases. What's
exactly going on, I don't know...

this shows that sometimes the old stuff works better than the new
stuff ;-)

kind regards,
h.rosmanith

Re: gcc-4.1.1 and kernel-2.4.32

[Alistair John Strachan]

On Wednesday 21 June 2006 15:25, Herbert Rosmanith wrote:
> > In effect (mainline) no. Linux 2.2 and 2.0 won't be fixed for the same
> > reason; called deep maintenance. 2.6 has been on the road since Dec 2003,
> > that's over 2 years. Do away with the old stuff.
>
> we are in the process of switching, which is not unproblematic. on
> the other hand, we have to support existing installations as well.

FWIW, distributions generally let you install older GCCs. Hopefully your 
distribution still has 2.95.3 in its repository, so you could install this to 
get a well tested (and probably smaller code generating) compiler for 2.4 
kernels. gcc -V <version> can be used to switch between them, if your 
distributor opts to install to the same prefix.

-- 
Cheers,
Alistair.

Third year Computer Science undergraduate.
1F2 55 South Clerk Street, Edinburgh, UK.

Re: gcc-4.1.1 and kernel-2.4.32

[Jesper Juhl]

On 21/06/06, Herbert Rosmanith <kernel@wildsau.enemy.org> wrote:
> a notebook which had problems with our software: a
> "toshiba portege m400". 2.4 seems to work so far, as does 2.6.16.
> I also tried 2.6.17, but get a strange problem: it simply hangs
> after writing "PCI: probing hardware" (or similar). A closer look
> reveals that it hangs in drivers/pci/probe.c, in pci_read_bases. What's
> exactly going on, I don't know...

May I suggest that you write up a complete bug report for that
regression (see the REPORTING-BUGS file for details) and send it to
LKML + Cc: relevant people from MAINTAINERS ?

-- 
Jesper Juhl <jesper.juhl@gmail.com>
Don't top-post  http://www.catb.org/~esr/jargon/html/T/top-post.html
Plain text mails only, please      http://www.expita.com/nomime.html

Re: gcc-4.1.1 and kernel-2.4.32

[Mikael Pettersson]

On Wed, 21 Jun 2006 15:17:34 +0200 (MET DST), Herbert Rosmanith wrote:
> trying to compile 2.4.32 with gcc-4.1.1 (probably any 4.x gcc?) produces
> a lot of errors, (i.e., declaration of symbols of different types and so on).
> 
> I wonder if it is planned to be fixed? No idea who's maintaining it - 
> in case you want to, I could send you diffs to make 2.4.32 compile.

Not reading LKML much, eh? Anyway, it's already being taken care of; see
<http://marc.theaimsgroup.com/?l=linux-kernel&m=115058555819917&w=2> for
well-tested patches for 2.4.33-rc1. They probably apply to 2.4.32 as well.

The powers that be have decreed that gcc-4 fixes won't be accepted
into the official 2.4 kernel, which is a pity since they are smaller
and simpler than the gcc-3.4 fixes which did get included.

/Mikael