If you compile your kernels with -fno-common, this problem would show
up. Andrea and a couple of the gcc guys, in a thread ~30 days ago,
recommended the use of -fno-common to build the kernel. I started using
it myself, and have picked up and fixed a few problems such as the one
that your patch fixes.
I sent a patch to Alan to add -fno-common to the command line of his
2.4.0-acXX patches, but it got dropped (presumeably too experimental or
In case anyone is curious, here is what 'info gcc' says about
> Allocate even uninitialized global variables in the bss section of
> the object file, rather than generating them as common blocks.
> This has the effect that if the same variable is declared (without
> `extern') in two different compilations, you will get an error
> when you link them. The only reason this might be useful is if
> you wish to verify that the program will work on other systems
> which always work this way.
-- Jeff Garzik | "You see, in this world there's two kinds of Building 1024 | people, my friend: Those with loaded guns MandrakeSoft | and those who dig. You dig." --Blondie - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to email@example.com Please read the FAQ at http://www.tux.org/lkml/