From: Adrian Bunk <bunk@fs.tum.de>
To: "Simon G. Vogl" <simon@tk.uni-linz.ac.at>,
linux-i2c@pelican.tk.uni-linz.ac.at, linux-net@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Subject: 2.5.55: Two global symbols driver_lock
Date: Fri, 10 Jan 2003 01:35:14 +0100 [thread overview]
Message-ID: <20030110003514.GA6626@fs.tum.de> (raw)
I got the following compile error in 2.5.55:
<-- snip -->
...
ld -m elf_i386 -r -o drivers/built-in.o drivers/pci/built-in.o
drivers/acpi/built-in.o drivers/pnp/built-in.o drivers/serial/built-in.o
drivers/parport/built-in.o drivers/base/built-in.o
drivers/char/built-in.o drivers/block/built-in.o drivers/misc/built-in.o
drivers/net/built-in.o drivers/media/built-in.o drivers/atm/built-in.o
drivers/ide/built-in.o drivers/scsi/built-in.o
drivers/ieee1394/built-in.o drivers/cdrom/built-in.o
drivers/video/built-in.o drivers/mtd/built-in.o
drivers/pcmcia/built-in.o drivers/block/paride/built-in.o
drivers/usb/built-in.o drivers/input/built-in.o
drivers/input/gameport/built-in.o drivers/input/serio/built-in.o
drivers/message/built-in.o drivers/i2c/built-in.o
drivers/telephony/built-in.o drivers/md/built-in.o
drivers/bluetooth/built-in.o drivers/hotplug/built-in.o
drivers/mca/built-in.o
drivers/i2c/built-in.o(.data+0x14): multiple definition of `driver_lock'
drivers/net/built-in.o(.data+0xcf14): first defined here
ld: Warning: size of symbol `driver_lock' changed from 4 to 20 in
drivers/i2c/built-in.o
make[1]: *** [drivers/built-in.o] Error 1
<-- snip -->
The offending files are:
drivers/i2c/i2c-core.c
drivers/net/aironet4500_proc.c
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
next reply other threads:[~2003-01-10 0:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-10 0:35 Adrian Bunk [this message]
2003-01-12 13:20 ` 2.5.55: Two global symbols driver_lock Muli Ben-Yehuda
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=20030110003514.GA6626@fs.tum.de \
--to=bunk@fs.tum.de \
--cc=linux-i2c@pelican.tk.uni-linz.ac.at \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-net@vger.kernel.org \
--cc=simon@tk.uni-linz.ac.at \
/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