From: Keith Owens <kaos@ocs.com.au>
To: Joseph Pingenot <trelane@digitasaru.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Build error on 2.5.20 under unstable debian
Date: Wed, 05 Jun 2002 17:38:26 +1000 [thread overview]
Message-ID: <23055.1023262706@kao2.melbourne.sgi.com> (raw)
In-Reply-To: Your message of "Wed, 05 Jun 2002 02:25:59 EST." <20020605022558.A2745@ksu.edu>
On Wed, 5 Jun 2002 02:25:59 -0500,
Joseph Pingenot <trelane@digitasaru.net> wrote:
>Hey, thanks for the nifty tool. What docs are available so that I can
> learn the Magic of the Script? :)
Years of hacking on ELF formats :(
>Error: ./drivers/usb/host/uhci-hcd.o .rodata refers to 00000f98 R_386_32 .text.exit
>Error: ./drivers/usb/host/built-in.o .rodata refers to 00000f98 R_386_32 .text.exit
Ignore drivers/usb/host/built-in.o, it is a conglomerate that contains
one object, the script cannot distinguish between that and a normal
object.
>Looks like uhci-hcd.o and built-in.o are the culprits. Now, if only
> I knew what the rest meant. :) They're referring to a symbol
> R_386_32? I'm going to assume this is an x86-based bit of stuff
> included from the x86-specific stuff. Teach me. ;)
R_386_32 is an ELF relocation type for ix86 binaries. It means that
uhci-hcd.c has code that refers to a function defined as __exit. The
only such function is uhci_hcd_cleanup but I cannot see where it is
being referenced. The USB people should be able to track this one
down.
next prev parent reply other threads:[~2002-06-05 7:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-04 15:36 Build error on 2.5.20 under unstable debian Joseph Pingenot
2002-06-04 22:28 ` Joseph Pingenot
2002-06-05 1:39 ` Keith Owens
2002-06-05 7:25 ` Joseph Pingenot
2002-06-05 7:38 ` Keith Owens [this message]
2002-06-05 8:18 ` Adrian Bunk
2002-06-05 17:21 ` Joseph Pingenot
2002-06-05 20:08 ` Adrian Bunk
2002-06-05 18:41 ` Greg KH
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=23055.1023262706@kao2.melbourne.sgi.com \
--to=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=trelane@digitasaru.net \
/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