All of lore.kernel.org
 help / color / mirror / Atom feed
* kernel vs. binutils: .exit.text problem
@ 2006-09-18 21:43 Michael 'Mickey' Lauer
  2006-09-18 22:43 ` Paul Sokolovsky
  0 siblings, 1 reply; 2+ messages in thread
From: Michael 'Mickey' Lauer @ 2006-09-18 21:43 UTC (permalink / raw)
  To: openembedded-devel

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?



-- 
Regards,

Michael 'Mickey' Lauer | FreeLancer | http://www.Vanille-Media.de





^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: kernel vs. binutils: .exit.text problem
  2006-09-18 21:43 kernel vs. binutils: .exit.text problem Michael 'Mickey' Lauer
@ 2006-09-18 22:43 ` Paul Sokolovsky
  0 siblings, 0 replies; 2+ messages in thread
From: Paul Sokolovsky @ 2006-09-18 22:43 UTC (permalink / raw)
  To: Michael 'Mickey' Lauer; +Cc: openembedded-devel

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




^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2006-09-18 22:47 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2006-09-18 21:43 kernel vs. binutils: .exit.text problem Michael 'Mickey' Lauer
2006-09-18 22:43 ` Paul Sokolovsky

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.