From: Alexander Dahl <post@lespocky.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH] add patch for building at91bootstrap with gcc 4.6.x
Date: Fri, 27 Jan 2012 10:25:21 +0100 [thread overview]
Message-ID: <a0bd5b5360afa16614127a351065f310@idefix.lespocky.dyndns.org> (raw)
In-Reply-To: <20120126153627.GA25996@pengutronix.de>
Hei Michael,
Am 26.01.2012 16:36, schrieb Michael Olbrich:
> Hmmm, I cannot trigger the problem (without the patch). Can you elaborate,
> what exact config/toolchain etc. your using?
See my mail from January 13th, where I described the problem. It occurs
with the OSELAS toolchain 2011.11.0 compiling for arm-v5te.
>>
>> Signed-off-by: Alexander Dahl <post@lespocky.de>
>> ---
>> .../0002-fix-overlap-linker-error.patch | 23 ++++++++++++++++++++
>> patches/Bootstrap-v1.16/series | 1 +
>> 2 files changed, 24 insertions(+), 0 deletions(-)
>> create mode 100755 patches/Bootstrap-v1.16/0002-fix-overlap-linker-error.patch
>>
>> diff --git a/patches/Bootstrap-v1.16/0002-fix-overlap-linker-error.patch b/patches/Bootstrap-v1.16/0002-fix-overlap-linker-error.patch
>> new file mode 100755
>> index 0000000..a86979f
>> --- /dev/null
>> +++ b/patches/Bootstrap-v1.16/0002-fix-overlap-linker-error.patch
>> @@ -0,0 +1,23 @@
>
> Please add a proper patch haeder here.
I don't understand what you mean. The inner patch added
(0002-fix-overlap-linker-error.patch) was generated with `quilt refresh
-u --no-timestamps --diffstat --sort --strip-trailing-whitespace` as I
always use it for our internal patches. The outer patch was created by
git the way you already applied patches from me. Which one is wrong and
in what way?
Greets
Alex
--
»With the first link, the chain is forged. The first speech censured,
the first thought forbidden, the first freedom denied, chains us all
irrevocably.« (Jean-Luc Picard, quoting Judge Aaron Satie)
*** GnuPG-FP: 02C8 A590 7FE5 CA5F 3601 D1D5 8FBA 7744 CC87 10D0 ***
--
ptxdist mailing list
ptxdist@pengutronix.de
next prev parent reply other threads:[~2012-01-27 9:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-26 15:04 Alexander Dahl
2012-01-26 15:36 ` Michael Olbrich
2012-01-27 9:25 ` Alexander Dahl [this message]
2012-01-30 14:20 ` Michael Olbrich
2012-01-31 16:54 ` Alexander Dahl
2012-01-31 19:29 ` Michael Olbrich
2012-02-01 11:54 ` [ptxdist] [PATCH] add patch fixing at91bootstrap build with gcc 4.6.x, and recreate patch series Alexander Dahl
2012-02-01 12:20 ` Michael Olbrich
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=a0bd5b5360afa16614127a351065f310@idefix.lespocky.dyndns.org \
--to=post@lespocky.de \
--cc=ptxdist@pengutronix.de \
/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