public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Arjan van de Ven <arjan@infradead.org>
Cc: linux-kernel@vger.kernel.org, Jeff Garzik <jgarzik@pobox.com>
Subject: Re: 2.6.16-git6: build failure: ne2k-pci: footbridge_defconfig
Date: Thu, 23 Mar 2006 16:55:58 +0000	[thread overview]
Message-ID: <20060323165558.GE25849@flint.arm.linux.org.uk> (raw)
In-Reply-To: <1143132732.3147.33.camel@laptopd505.fenrus.org>

On Thu, Mar 23, 2006 at 05:52:12PM +0100, Arjan van de Ven wrote:
> On Thu, 2006-03-23 at 16:41 +0000, Russell King wrote:
> > 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.
> 
> 
> that's a gcc bug; probably arm specific even?

It's gcc 4.01... the kautobuild folk are going to try gcc 4.04 instead.

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

  reply	other threads:[~2006-03-23 16:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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

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=20060323165558.GE25849@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=arjan@infradead.org \
    --cc=jgarzik@pobox.com \
    --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