Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc 4.2.4: Fix builds for i686 when headers are not present.
Date: Wed, 25 Aug 2010 17:12:03 +0200	[thread overview]
Message-ID: <87r5hmwwu4.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1281652484-27944-1-git-send-email-raj.khem@gmail.com> (Khem Raj's message of "Thu, 12 Aug 2010 15:34:44 -0700")

>>>>> "Khem" == Khem Raj <raj.khem@gmail.com> writes:

 Khem> with this I could reproduce this issue. Here is a patch for gcc
 Khem> that will get you over this hump drop it into toolchain/gcc/4.2.4/
 Khem> and rebuild the first problem will be ok. The problem with locales
 Khem> is a separate issue and is not related to the toolchain build
 Khem> sequence change.

 Khem> If this works Then consider applying this patch to BR

Committed, thanks.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-08-25 15:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 22:34 [Buildroot] [PATCH] gcc 4.2.4: Fix builds for i686 when headers are not present Khem Raj
2010-08-25 15:12 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-08-11 20:46 Khem Raj

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=87r5hmwwu4.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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