🚀 go-pugleaf

Rene Crettol <rcrettol@datanetworks.ch> wrote:
> M�chte den Kernel 2.2.0 in SuSE Linux 6.0 verwenden.
> W�hrent "make zImage" trat ein Fehler auf

2.2.1 is now out. Please try this one (get the patch from
http://www.ch.kernel.org/pub/linux/kernel/2.2/patch-2.2.1.bz2
or similar)

Also, if it still fails, consult linux/CHANGES to be *sure*
that you have all libraries, compilers, etc, able to compile
2.2.x.

I don't have SuSE 6.0 yet, but until I try it, I will not
believe the marketing that they are ``2.2''-ready.

Anyway, do you really want to use 2.2 TODAY ?  Why not wait
some time, and use 2.0.36 until 2.2 has stabilized ?  Remember
how many buggy versions there were in 2.0 after 1.3 stabilization ?

> Hat jemand eine Idee was das Problem sein k�nnte?

On a SuSE 5.2 Linux box, no changes (this violates the linux/CHANGES),
2.2.1 compiles and run somewhat (I can compile the kernel itself).

However I will not use it for production because
   1. there are many things not upto-date in 5.2 (probably much more
      than in 6.0)
   2. 2.2.1 is still, for me, unstable, because not widely tested.

> checksum.c:105: `csum_partial_copy' previously defined here
> {standard input}: Assembler messages:
> {standard input}:188: Fatal error: Symbol csum_partial_copy already
> defined.

Looks really like 2.2.0 was badly created (bad set of patches, or
maybe 2.2.0 doesn't work --- try 2.2.1)