All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: Re: psuedo-native strangeness on 64 bit build machine
Date: Thu, 01 Mar 2012 02:33:29 -0800	[thread overview]
Message-ID: <4F4F5079.1050608@gmail.com> (raw)
In-Reply-To: <CAGDS+nnd_hZnxgX1JfKMksxmfREYjqEYFYN+Yhj=sgffUsCXNA@mail.gmail.com>

On 02/29/2012 07:12 AM, Steve Sakoman wrote:
> On Wed, Feb 29, 2012 at 6:22 AM, Steve Sakoman <sakoman@gmail.com> wrote:
>> On Wed, Feb 29, 2012 at 12:45 AM, Petr Štetiar <ynezz@true.cz> wrote:
> 
>>> Now it's impossible to finish the build, the most noticeable failure is gcc,
>>> which fails for me in patching task due to the parallel build settings.
>>> Changing the parallel settings back to 1 helps here also.
>>
>> I just tried building gcc and can confirm that it fails for me on the
>> 64 bit build machine.
> 
> For me, a -c cleansstate gcc and then a rebuild resulted in a
> successful gcc build.  I did not need to turn off parallel builds.
> 

just add NO32LIBS = "1" to your local.conf

> Steve
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core




  reply	other threads:[~2012-03-01 10:42 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29  4:35 psuedo-native strangeness on 64 bit build machine Steve Sakoman
2012-02-29  5:13 ` Mark Hatle
2012-02-29  5:29   ` Steve Sakoman
2012-02-29  5:36     ` Mark Hatle
2012-02-29  8:45   ` Petr Štetiar
2012-02-29 14:22     ` Steve Sakoman
2012-02-29 15:12       ` Steve Sakoman
2012-03-01 10:33         ` Khem Raj [this message]
2012-03-01 14:30           ` Steve Sakoman

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=4F4F5079.1050608@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.