Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 3 Mar 2012 21:13:38 -0200	[thread overview]
Message-ID: <20120303211338.14fe3545@gmail.com> (raw)
In-Reply-To: <20120301181031.GA3915@tarshish>

On Thu, 1 Mar 2012 20:10:32 +0200
Baruch Siach <baruch@tkos.co.il> wrote:
<...> 
> But BR2_GCC_VERSION_4_6_X is only available when selecting internal 
> toolchains. See toolchain/toolchain-buildroot/Config.in.

Would setting it (on the command line) produce any side-effect?

> Doesn't the patch from r183512 fix this bug?

What is "r183512" supposed to mean?
-------------- 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/20120303/0f46aab0/attachment.asc>

  reply	other threads:[~2012-03-03 23:13 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 [this message]
2012-03-05  5:19         ` Baruch Siach
2012-03-05  6:45           ` Ismael Luceno
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=20120303211338.14fe3545@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