From: Ismael Luceno <ismael.luceno@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x
Date: Mon, 5 Mar 2012 04:45:14 -0200 [thread overview]
Message-ID: <20120305044514.077a2dd7@gmail.com> (raw)
In-Reply-To: <20120305051937.GA26631@sapphire.tkos.co.il>
On Mon, 5 Mar 2012 07:19:37 +0200
Baruch Siach <baruch@tkos.co.il> wrote:
> On Sat, Mar 03, 2012 at 09:13:38PM -0200, Ismael Luceno wrote:
> > On Thu, 1 Mar 2012 20:10:32 +0200
> > Baruch Siach <baruch@tkos.co.il> wrote:
> > > Doesn't the patch from r183512 fix this bug?
> >
> > What is "r183512" supposed to mean?
>
> This the Subversion commit mentioned in comment #20 of Bugzilla bug
> #48308 that you linked to
<...>
Oh, I thought you were talking about buildroot.
> (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48308). Comment #21
> seems to indicate that this fix hasn't been backported to gcc 4.6.x.
Probably not hitting anytime soon.
> Maybe a better solutions would be to add this patch Buildroot's
> internal gcc.
Indeed.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20120305/16c2119c/attachment.asc>
next prev parent reply other threads:[~2012-03-05 6:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-29 23:27 [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x Ismael Luceno
2012-02-29 23:27 ` [Buildroot] [PATCH 2/2] openssl: Add -march and -mcpu flags Ismael Luceno
2012-03-01 5:37 ` [Buildroot] [PATCH 1/2] openssl: Fix build on ARM with GCC 4.6.x Baruch Siach
2012-03-01 7:32 ` Thomas Petazzoni
2012-03-01 17:32 ` Ismael Luceno
2012-03-01 18:10 ` Baruch Siach
2012-03-03 23:13 ` Ismael Luceno
2012-03-05 5:19 ` Baruch Siach
2012-03-05 6:45 ` Ismael Luceno [this message]
2012-03-06 15:21 ` Gustavo Zacarias
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=20120305044514.077a2dd7@gmail.com \
--to=ismael.luceno@gmail.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