From: Dale Farnsworth <dale@farnsworth•org>
To: Kumar Gala <galak@kernel•crashing.org>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: binutils 2.19 issue with kernel link
Date: Thu, 9 Jul 2009 12:06:21 -0700 [thread overview]
Message-ID: <20090709190621.GB6549@farnsworth.org> (raw)
In-Reply-To: <29A5B467-BD0F-4270-B5A4-EF79D9405E28@kernel.crashing.org>
On Thu, Jul 09, 2009 at 01:14:28PM -0500, Kumar Gala wrote:
> On Jul 9, 2009, at 11:39 AM, Dale Farnsworth wrote:
>> We have found the following workaround to be useful.
>> Thanks to Andrew Jenner at Code Sourcery.
>>
>> -Dale
>>
>> Dale Farnsworth
>> MontaVista Software
>>
>> diff --git a/arch/powerpc/kernel/vmlinux.lds.S b/arch/powerpc/kernel/
>> vmlinux.lds.S
>> index acf237f..34b0181 100644
>> --- a/arch/powerpc/kernel/vmlinux.lds.S
>> +++ b/arch/powerpc/kernel/vmlinux.lds.S
>> @@ -282,4 +282,7 @@ SECTIONS
>> . = ALIGN(PAGE_SIZE);
>> _end = . ;
>> PROVIDE32 (end = .);
>> +
>> +#undef PPC
>> + .PPC.EMB.apuinfo 0 : { *(.PPC.EMB.apuinfo) }
>> }
>
> Is there any plans to fix binutils or is this viewed as not a binutils
> regression?
It sure looks like a regression to me, but I don't have details on
a potential fix.
-Dale
prev parent reply other threads:[~2009-07-09 19:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 22:41 binutils 2.19 issue with kernel link Kumar Gala
2009-07-08 23:39 ` Alan Modra
2009-07-09 2:40 ` Kumar Gala
2009-07-09 3:39 ` Kumar Gala
2009-07-09 3:52 ` Kumar Gala
2009-07-09 4:40 ` Alan Modra
2009-07-09 15:22 ` Kumar Gala
2009-07-09 19:31 ` Edmar Wienskoski-RA8797
2009-07-10 4:11 ` Alan Modra
2009-07-10 15:34 ` Kumar Gala
2009-07-10 4:15 ` Alan Modra
2009-07-10 14:37 ` Kumar Gala
2009-07-10 15:27 ` Kumar Gala
2009-07-11 0:05 ` Alan Modra
2009-07-11 0:08 ` Alan Modra
2009-07-09 16:39 ` Dale Farnsworth
2009-07-09 18:14 ` Kumar Gala
2009-07-09 19:06 ` Dale Farnsworth [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=20090709190621.GB6549@farnsworth.org \
--to=dale@farnsworth$(echo .)org \
--cc=galak@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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