From: Paul Sokolovsky <pmiscml@gmail.com>
To: Michael 'Mickey' Lauer <mickey@tm.informatik.uni-frankfurt.de>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: kernel vs. binutils: .exit.text problem
Date: Tue, 19 Sep 2006 01:43:15 +0300 [thread overview]
Message-ID: <1228985494.20060919014315@gmail.com> (raw)
In-Reply-To: <1158615816.14182.13.camel@gandalf.tm.informatik.uni-frankfurt.de>
Hello Michael,
Tuesday, September 19, 2006, 12:43:36 AM, you wrote:
> I'm building a 2.6.17.7 kernel for arm using gcc 4.1.1 and binutils
> 2.17:
> | make[1]: Leaving directory kernel-2.6.17.7 | LD .tmp_vmlinux1
> | `.exit.text' referenced in section `.init.text' of drivers/built-in.o:
> defined in discarded section `.exit.text' of drivers/built-in.o
> | make: *** [.tmp_vmlinux1] Error 1
> The same kernel is compiled fine (and runs, btw.) w/ binutils 2.15.94.1.
> I can't downgrade binutils because the older binutils don't compile
> other stuff w/ recent gcc's. binutils 2.16 even SIGSEGVs for some
> packages.
> Older binutils treated this as a warning, not an error. Do you have any
> idea how I could revert binutils 2.17 to this behaviour? Or
> alternatively, how can I find and fix the offending
> driver in the said kernel?
That's kernel issue, upgrade to 2.6.18 (even rc) ;-) . On HH.org, we faced
this with pxa2xx_udc driver. Fix was already in mainline, so we just backported
patch:
http://kernel.org/git/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=a353678d3136306c1d00f0d2319de1dac8a6b1db
(actually applied as is).
--
Best regards,
Paul mailto:pmiscml@gmail.com
prev parent reply other threads:[~2006-09-18 22:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 21:43 kernel vs. binutils: .exit.text problem Michael 'Mickey' Lauer
2006-09-18 22:43 ` Paul Sokolovsky [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=1228985494.20060919014315@gmail.com \
--to=pmiscml@gmail.com \
--cc=mickey@tm.informatik.uni-frankfurt.de \
--cc=openembedded-devel@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.