From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] gcc: fix libstdc++_pic for AVR32
Date: Fri, 23 Aug 2013 06:59:36 +0200 [thread overview]
Message-ID: <20130823065936.18a7d3e0@skate> (raw)
In-Reply-To: <1376025370-9467-1-git-send-email-alexander.lukichev@gmail.com>
Dear Alexander Lukichev,
On Fri, 9 Aug 2013 08:16:10 +0300, Alexander Lukichev wrote:
> It is not clear why 300-libstdc++-pic.patch pre-applied to
> gcc-4.2.2-avr32-2.1.5 seems to have come from some older version
> of gcc (as early as 4.0.3). This older patch incorrectly refers to
> object files to be included in the library libstdc++_pic.a as *.o,
> while their location seems to be in .libs/*.o (see the contents at
> e.g. https://github.com/ZigFisher/Midge/blob/master/toolchain/gcc/4.0.3/300-libstdc%2B%2B-pic.patch ).
> The same patch for gcc 4.1.0 refers to the files as .libs/*.o (see
> https://github.com/ZigFisher/Midge/blob/master/toolchain/gcc/4.1.0/300-libstdc%2B%2B-pic.patch ).
> This patch corrects rules in Makefile.in.
>
> Signed-off-by: Alexander Lukichev <alexander.lukichev@gmail.com>
Applied, thanks.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-08-23 4:59 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 5:16 [Buildroot] [PATCH 1/1] gcc: fix libstdc++_pic for AVR32 Alexander Lukichev
2013-08-10 19:06 ` Thomas Petazzoni
2013-08-10 19:47 ` Simon Dawson
2013-08-12 7:21 ` Alexander Lukichev
2013-08-20 11:02 ` Simon Dawson
2013-08-23 4:59 ` Thomas Petazzoni [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=20130823065936.18a7d3e0@skate \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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