From: hjl@lucon.org (H.J. Lu)
To: tm@netcom.com (Toshiyasu Morita)
Cc: gas2@cygnus.com
Subject: Re: another binutils-2.8.1 bug?
Date: Fri, 09 Jan 1998 20:22:00 -0000 [thread overview]
Message-ID: <m0xqsRE-0004ecC@ocean.lucon.org> (raw)
In-Reply-To: <199801040802.AAA17553@netcom9.netcom.com>
>
>
>
> Host: i386-linux
> Target: m68k-linux
> Tool: binutils-2.8.1 ld using m68k-elf
>
> I seem to have found a bug in binutils-2.8.1. The linker fails to find
> a reference to "putpacket()" even though it is contained in one of the
> object files.
>
> Here's the output:
>
> m68k-linux-ld -m m68kelf -T /usr/src/linux-sun3-2.1.72/arch/m68k/vmlinux-sun3.lds
> -N arch/m68k/kernel/head.o init/main.o init/version.o \
> arch/m68k/kernel/kernel.o arch/m68k/mm/mm.o kernel/kernel.o mm/mm.o fs/fs.o ipc/ipc.o arch/m68k/sun3/sun3.o arch/m68k/sun3/prom/promlib.a arch/m68k/fpsp040/fpsp.o
> \
> fs/filesystems.a \
> net/network.a \
> drivers/block/block.a drivers/char/char.a drivers/misc/misc.a drivers/net/net.a drivers/video/video.a \
> /usr/src/linux-sun3-2.1.72/lib/lib.a arch/m68k/lib/lib.a \
> -o vmlinux -M > ld.lst
> arch/m68k/sun3/prom/promlib.a(printf.o): In function `prom_printf':
> /usr/src/linux-sun3-2.1.72/arch/m68k/sun3/prom/printf.c:46: undefined reference to `putpacket'
> make: *** [vmlinux] Error 1
> [root@piglet linux]# m68k-linux-objdump --syms arch/m68k/kernel/kernel.o | grep putpacket
> 000085d4 l F .text 000000ac putpacket
Doesn't 'l' mean "local"?
> [root@piglet linux]#
>
> I have uploaded the files necessary to replicate this problem to:
>
> ftp://shell14.ba.best.com/pub.t/tm2/bug2.tar.gz
>
> Toshi
>
>
>
--
H.J. Lu (hjl@gnu.org)
prev parent reply other threads:[~1998-01-09 20:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-01-04 0:02 Toshiyasu Morita
1998-01-09 20:22 ` H.J. Lu [this message]
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=m0xqsRE-0004ecC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=gas2@cygnus.com \
--cc=tm@netcom.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).