From: Andreas Steinmetz <ast@domdv.de>
To: linux.nics@intel.com, linux-kernel@vger.kernel.org
Subject: 2.4.20pre5 e100 build error + trivial fix
Date: Thu, 05 Sep 2002 01:12:49 +0200 [thread overview]
Message-ID: <3D769371.6000009@domdv.de> (raw)
[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]
Hi,
the e100 driver in 2.4.20pre5 fails to build due to a static procedure
declaration with an unresolved symbol (see below), trivial patch to fix
this is attached.
ld -m elf_i386 -T
/usr/src/ARCHIVE/kernel-2.4.20pre5/linux/arch/i386/vmlinux.lds -e stext
arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/main.o
init/version.o init/do_mounts.o \
--start-group \
arch/i386/kernel/kernel.o arch/i386/mm/mm.o kernel/kernel.o
mm/mm.o fs/fs.o ipc/ipc.o \
drivers/char/char.o drivers/block/block.o drivers/misc/misc.o
drivers/net/net.o drivers/media/media.o drivers/ide/idedriver.o
drivers/cdrom/driver.o drivers/pci/driver.o drivers/video/video.o \
net/network.o \
\
/usr/src/ARCHIVE/kernel-2.4.20pre5/linux/arch/i386/lib/lib.a
/usr/src/ARCHIVE/kernel-2.4.20pre5/linux/lib/lib.a
/usr/src/ARCHIVE/kernel-2.4.20pre5/linux/arch/i386/lib/lib.a \
--end-group \
-o vmlinux
drivers/net/net.o: In function `e100_diag_config_loopback':
drivers/net/net.o(.text+0x8a74): undefined reference to
`e100_force_speed_duplex'
--
Andreas Steinmetz
D.O.M. Datenverarbeitung GmbH
[-- Attachment #2: e100_phy.diff --]
[-- Type: text/plain, Size: 276 bytes --]
--- drivers/net/e100/e100_phy.c.orig 2002-09-05 00:35:38.000000000 +0200
+++ drivers/net/e100/e100_phy.c 2002-09-05 01:03:32.000000000 +0200
@@ -622,7 +622,7 @@
* Returns: void
*
*/
-static void
+void
e100_force_speed_duplex(struct e100_private *bdp)
{
u16 control;
next reply other threads:[~2002-09-04 23:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-04 23:12 Andreas Steinmetz [this message]
2002-09-05 1:56 ` 2.4.20pre5 e100 build error + trivial fix Jeff Garzik
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=3D769371.6000009@domdv.de \
--to=ast@domdv.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux.nics@intel.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