From: "H. J. Lu" <hjl@lucon.org>
To: linux-ia64@vger.kernel.org
Subject: Re: 2.6.3 compilation problem
Date: Fri, 12 Mar 2004 05:42:04 +0000 [thread overview]
Message-ID: <20040312054204.GB16214@lucon.org> (raw)
In-Reply-To: <002f01c40735$8d2cc880$39624c0f@india.hp.com>
From my very old binutils release note:
---
3. Update handling relocations against the discarded sections. You may
need to apply the kernel patch enclosed here to your kernel source. If
you still see things like
drivers/char/char.o(.data+0x46b4): undefined reference to `local symbols in discarded section .text.exit'
in the final kernel link, that means you have compiled a driver into
the kernel which has a reference to the symbol in a discarded section.
Please check all the builtin drivers and search for things like
static struct pci_driver xxx_pci_driver = {
...
remove: xxx_remove,
...
};
Then check to see if xxx_remove is marked with __devexit like
static void __devexit
xxx_remove (struct pci_dev *dev)
{
...
}
which means it will be discarded if the driver is builtin. If
xxx_remove may be discarded, please make sure there is
#ifdef MODULE
remove: xxx_remove,
#endif
so that xxx_remove won't be included when the driver is builtin.
---
Hope it help.
H.J.
On Fri, Mar 12, 2004 at 11:52:59AM +0800, Liu, Benjamin wrote:
> Sourav,
>
> Could you please send out your configure file in attachment? I can not reproduce your issue even when I configured CONFIG_SERIO.
>
> Ken, it's too early to make any judgement.
>
> Thanks,
> Pingping (Benjamin) Liu
> Intel China Software Center
>
>
> >-----Original Message-----
> >From: Chen, Kenneth W
> >Sent: 2004年3月12日 2:38
> >To: Liu, Benjamin; Sourav Sen; linux-ia64@vger.kernel.org
> >Subject: RE: 2.6.3 compilation problem
> >
> >
> >>>>>> Liu, Benjamin wrote on Thu, March 11, 2004 12:33 AM
> >> To workaround the problem, you can append
> >__attribute__((weak)) to the
> >> declaration of those discarded symbols defined in section
> >".exit.text".
> >>
> >> The device driver author might be able to answer why it is
> >written that
> >> way.
> >
> >The linker gets the award for least informative in this case,
> >and it just
> >plain misleading. The culprit isn't the one printed. It lies
> >somewhere
> >else.
> >
> >- Ken
> >
> >
> >
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2004-03-12 5:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-11 6:55 2.6.3 compilation problem Sourav Sen
2004-03-11 6:57 ` Zhang, Yanmin
2004-03-11 8:32 ` Liu, Benjamin
2004-03-11 18:37 ` Kenneth Chen
2004-03-12 3:52 ` Liu, Benjamin
2004-03-12 5:42 ` H. J. Lu [this message]
2004-03-12 5:54 ` Chen, Kenneth W
2004-03-12 6:01 ` Keith Owens
2004-03-12 9:15 ` Liu, Benjamin
2004-03-12 9:25 ` Liu, Benjamin
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=20040312054204.GB16214@lucon.org \
--to=hjl@lucon.org \
--cc=linux-ia64@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