From: Ed Sweetman <safemode@speakeasy.net>
To: linux-kernel@vger.kernel.org
Subject: fs/fs.o linking error in 2.5.25-dj2
Date: 13 Jul 2002 00:54:01 -0400 [thread overview]
Message-ID: <1026536041.1203.107.camel@psuedomode> (raw)
When compiling with the 2.5 ide subsystem i get undefined references to
__udivdi3
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 /usr/src/linux-2.5.25/arch/i386/lib/lib.a lib/lib.a /usr/src/linux-2.5.25/arch/i386/lib/lib.a drivers/built-in.o sound/sound.o arch/i386/pci/pci.o net/network.o --end-group -o vmlinux
fs/fs.o: In function `proc_pid_stat':
fs/fs.o(.text+0x1ff3f): undefined reference to `__udivdi3'
fs/fs.o: In function `kstat_read_proc':
fs/fs.o(.text+0x20fc8): undefined reference to `__udivdi3'
fs/fs.o(.text+0x2105e): undefined reference to `__udivdi3'
I've attached my config along with it. There is also a missing
semicolon on line 70 of drivers/char/agp/agpgart_be-i8x0.c
next reply other threads:[~2002-07-13 4:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-13 4:54 Ed Sweetman [this message]
2002-07-13 5:11 ` fs/fs.o linking error in 2.5.25-dj2 Ed Sweetman
2002-07-13 7:45 ` [Patch] " Tim Schmielau
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=1026536041.1203.107.camel@psuedomode \
--to=safemode@speakeasy.net \
--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