public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
* 2.6.16-git6: build failure: ne2k-pci: footbridge_defconfig
@ 2006-03-23 16:41 Russell King
  2006-03-23 16:52 ` Arjan van de Ven
  0 siblings, 1 reply; 6+ messages in thread
From: Russell King @ 2006-03-23 16:41 UTC (permalink / raw)
  To: linux-kernel, Jeff Garzik

Building the ARM footbridge_defconfig provokes this build error:

  CC      drivers/net/ne2k-pci.o
drivers/net/ne2k-pci.c:123: error: pci_clone_list causes a section type conflict
make[2]: *** [drivers/net/ne2k-pci.o] Error 1
make[1]: *** [drivers/net] Error 2
make: *** [drivers] Error 2
make: Leaving directory `/var/tmp/kernel-orig'

static const struct {
        char *name;
        int flags;
} pci_clone_list[] __devinitdata = {

const data can't be __devinitdata.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

^ permalink raw reply	[flat|nested] 6+ messages in thread
* Re: 2.6.16-git6: build failure: ne2k-pci: footbridge_defconfig
@ 2006-03-28 12:02 Mikael Pettersson
  0 siblings, 0 replies; 6+ messages in thread
From: Mikael Pettersson @ 2006-03-28 12:02 UTC (permalink / raw)
  To: rmk+lkml; +Cc: akpm, arjan, jgarzik, linux-kernel

On Thu, 23 Mar 2006 17:40:14 +0000, Russell King wrote:
>> It's gcc 4.01... the kautobuild folk are going to try gcc 4.04 instead.
>
>Actually, given that it also appears with gcc 3.3, I'd like to request
>that the change (along with all the other const __devinitdata's) are
>backed out.
>
>The comments I'm hearing about gcc 4.1 on ARM indicate that it's a case
>of "there be big beasts there, don't touch with a barge pole".  To quote
>some comments about gcc 4.1 on ARM:
>
>"yeah, 4.1 is quite bad on arm.  it's supposed to have all the EABI bits,
> but it can't even build itself without ICEing and segfaulting left right
> and center"
>
>"the debian arm failures with gcc 4.1 are just scary.  the current gcc
> 4.1s miscompile even very basic for/while loops"
>
>which probably leaves ARM folk with a very narrow set of working gcc
>versions.
>
>So, I've no idea at present which gcc version we should be considering
>nominating as "the sole gcc version the kernel supports".

Just a data point...

My ARM GCCs are configured for the default arm-linux ABI,
not the EABI, and gcc-4.0.3 and gcc-4.1 both appear to be
solid for user-space code; they also bootstrap themselves
(on an ARM) just fine. I haven't used them for kernels however.

On the other hand, gcc-3.3.6 and gcc-3.4.6 both require several
add-on patches to fix incorrect code generation, and even then
there are a couple of known unfixed bugs (PR25133 and PR26463 in
particular; PR25133 can be worked around but PR26463 scares me).

/Mikael

^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2006-03-28 12:03 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-03-23 16:41 2.6.16-git6: build failure: ne2k-pci: footbridge_defconfig Russell King
2006-03-23 16:52 ` Arjan van de Ven
2006-03-23 16:55   ` Russell King
2006-03-23 17:40     ` Russell King
2006-03-23 18:11       ` Arjan van de Ven
  -- strict thread matches above, loose matches on Subject: below --
2006-03-28 12:02 Mikael Pettersson

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox