From: "Johnnie Q. Hacker" <trelane@paulus.neurotek.dnsalias.com>
To: linux-kernel@vger.kernel.org
Subject: 2.5.30: undefined references in sound/sound.o and net/network.o
Date: Sun, 11 Aug 2002 14:28:58 -0500 [thread overview]
Message-ID: <20020811192858.GA5809@digitasaru.net> (raw)
Got the following errors when making bzImage for 2.5.30. Thought y'all
might like to see 'em.
ld -m elf_i386 -T arch/i386/vmlinux.lds -e stext arch/i386/kernel/head.o arch/i386/kernel/init_task.o init/init.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 security/built-in.o /usr/local/src/kernel/linux-2.5.30/arch/i386/lib/lib.a lib/lib.a /usr/local/src/kernel/linux-2.5.30/arch/i386/lib/lib.a drivers/built-in.o sound/sound.o arch/i386/pci/pci.o net/network.o --end-group -o vmlinux
sound/sound.o: In function `snd_cs4281_gameport':
sound/sound.o(.text+0x2f739): undefined reference to `gameport_register_port'
sound/sound.o: In function `snd_cs4281_free':
sound/sound.o(.text+0x2f755): undefined reference to `gameport_unregister_port'
net/network.o: In function `sock_init':
net/network.o(.text.init+0x65): undefined reference to `bluez_init'
make: *** [vmlinux] Error 1
--
Joseph======================================================jap3003@ksu.edu
"Linux has restored innovation in software development, and the form of
this innovation is not in finding new ways to charge customers or lock them
in to obscure file formats. Linux innovation is about the individual, about
freedom, and yes, about just working." --Brian Jamison
reply other threads:[~2002-08-12 22:20 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020811192858.GA5809@digitasaru.net \
--to=trelane@paulus.neurotek.dnsalias.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
all inboxes | Powered by JetHome®