From: Segher Boessenkool <segher@kernel.crashing.org>
To: Chuck Meade <chuckmeade@mindspring.com>
Cc: linuxppc-dev list <linuxppc-dev@ozlabs.org>,
Sean MacLennan <smaclennan@pikatech.com>
Subject: Re: [PATCH] powerpc: Fix build bug with binutils < 2.18 and GCC < 4.2
Date: Fri, 25 Jul 2008 02:18:54 +0200 [thread overview]
Message-ID: <aad162859ed07fa69015df3d8b2b3e69@kernel.crashing.org> (raw)
In-Reply-To: <488912BC.6040706@mindspring.com>
>>> I can help you by testing on 2.15. Send me alternate vmlinux.lds.S
>>> files
>>> to try, and I will test and get back to you ASAP.
>>
>> No, I will not send you randomly changed source files and hope they
>> will do something useful for you. Instead, why not provide me the
>> information I asked for? What target (arch/powerpc it sounds like?)
>> What _exact_ binutils version (FSF 2.15?) What _exact_ GCC version
>> (FSF 3.4.4?) What Linux config (either the full .config, or the
>> name of a defconfig)?
>
> No problem -- I thought it would be helpful to offer to test changes
> for you,
> so we could work together toward a solution.
Sure, and thanks for that! I need to be able to reproduce it myself
to create a patch in the first place though (or spend a few hundred
hours in a senseless guessing game) :-)
I now managed to reproduce it with 2.15 on powerpc64. You should see
the patch soon (I sent it, but for seem reason it takes a while to
get through ozlabs, half an hour or so the last time).
Please test, and thank you! Reply to the patch mail saying if it
worked please (Jon, Sean, you as well?).
Segher
prev parent reply other threads:[~2008-07-25 0:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 23:03 [PATCH] powerpc: Fix build bug with binutils < 2.18 and GCC < 4.2 Segher Boessenkool
[not found] ` <48872AB4.3010001@mindspring.com>
[not found] ` <bd512e1b36a954819f09379908e342fb@kernel.crashing.org>
[not found] ` <48882217.5010609@mindspring.com>
2008-07-24 22:27 ` Segher Boessenkool
2008-07-24 23:39 ` Chuck Meade
2008-07-25 0:18 ` Segher Boessenkool [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=aad162859ed07fa69015df3d8b2b3e69@kernel.crashing.org \
--to=segher@kernel.crashing.org \
--cc=chuckmeade@mindspring.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=smaclennan@pikatech.com \
/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;
as well as URLs for NNTP newsgroup(s).