From: Aioanei Rares <krnl.list@gmail.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BUG : drivers/staging/comedi/drivers/cb_pcidio.o linking error
Date: Thu, 17 Sep 2009 16:40:50 +0300 [thread overview]
Message-ID: <4AB23C62.9070807@gmail.com> (raw)
Trying to compile the latest git kernel pulled today (16.09) greeted me
with this error :
BUILD arch/x86/boot/bzImage
Root device is (8, 2)
Setup is 13996 bytes (padded to 14336 bytes).
System is 2381 kB
CRC bfd3396b
Kernel: arch/x86/boot/bzImage is ready (#7)
Building modules, stage 2.
MODPOST 1250 modules
WARNING: drivers/staging/comedi/drivers/cb_pcidio.o(.text+0xe5): Section
mismatch in reference from the function pcidio_attach() to the variable
.devinit.rodata:pcidio_pci_table
The function pcidio_attach() references
the variable __devinitconst pcidio_pci_table.
This is often because pcidio_attach lacks a __devinitconst
annotation or the annotation of pcidio_pci_table is wrong.
ERROR: "per_cpu__cpu_llc_id" [drivers/edac/edac_core.ko] undefined!
make[1]: *** [__modpost] Error 1
make: *** [modules] Error 2
I was compiling with make CONFIG_DEBUG_SECTION_MISMATCH=y all
on a Debian testing/unstable system with gcc arares@debian:~/linux-2.6$
gcc -v
Using built-in specs.
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Debian 4.3.4-2'
--with-bugurl=file:///usr/share/doc/gcc-4.3/README.Bugs
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
--enable-shared --enable-multiarch --enable-linker-build-id
--with-system-zlib --libexecdir=/usr/lib --without-included-gettext
--enable-threads=posix --enable-nls
--with-gxx-include-dir=/usr/include/c++/4.3 --program-suffix=-4.3
--enable-clocale=gnu --enable-libstdcxx-debug --enable-objc-gc
--enable-mpfr --with-tune=generic --enable-checking=release
--build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.3.4 (Debian 4.3.4-2)
and make arares@debian:~/linux-2.6$ make -v
GNU Make 3.81
Copyright (C) 2006 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
This program built for x86_64-pc-linux-gnu
binutils :
arares@debian:~/linux-2.6$ as -v
GNU assembler version 2.19.91 (x86_64-linux-gnu) using BFD version (GNU
Binutils for Debian) 2.19.91.20090910
arares@debian:~/linux-2.6$ ld -v
GNU ld (GNU Binutils for Debian) 2.19.91.20090910
...and a fully updated system.
next reply other threads:[~2009-09-16 13:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-17 13:40 Aioanei Rares [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-09-16 10:29 BUG: oops in gss_validate on 2.6.31 Bastian Blank
2009-09-17 12:16 ` BUG : drivers/staging/comedi/drivers/cb_pcidio.o linking error Aioanei Rares
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=4AB23C62.9070807@gmail.com \
--to=krnl.list@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rares.aioanei@gmail.com \
/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