Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot fails at libstdc++
Date: Mon, 7 Jan 2008 16:16:13 +0100	[thread overview]
Message-ID: <029101c85141$ba33f330$030514ac@atmel.com> (raw)
In-Reply-To: 36163.1199717483@powersmiths.com

> Hi all,
> 
> I am having a problem with taking the buildroot process pass the libstdc++ phase.
> Here is my setup:

> buildroot snapshot 2008-01-02

> binutils 2.18
> kernel   2.6.22.10
> gcc      3.4.6
> uClibc   0.9.29

Maybe you should try with gcc-4.2.1
Best Regards
Ulf Samuelsson

  reply	other threads:[~2008-01-07 15:16 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-07 14:51 [Buildroot] Buildroot fails at libstdc++ piotr at powersmiths.com
2008-01-07 15:16 ` Ulf Samuelsson [this message]
2008-01-07 16:05   ` Piotr Grudzinski
2008-01-07 16:09 ` Atle Nissestad
2008-01-07 16:35   ` Piotr Grudzinski
2008-01-07 17:36     ` Ivan Kuten
2008-01-07 18:19       ` Piotr Grudzinski
2008-01-07 20:44         ` Atle Nissestad
2008-01-07 22:52           ` Piotr Grudzinski

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='029101c85141$ba33f330$030514ac@atmel.com' \
    --to=ulf@atmel.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