Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Atle Nissestad <atle@nissestad.no>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot fails at libstdc++
Date: Mon, 7 Jan 2008 17:09:25 +0100	[thread overview]
Message-ID: <200801071709.25722.atle@nissestad.no> (raw)
In-Reply-To: <36163.1199717483@powersmiths.com>

On Monday 7. January 2008 15:51:23 piotr at powersmiths.com wrote:
>  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
>
>  generic arm, nommu, no FP, soft-float, little-endian (all configs
> attached) no user apps - just the toolchain
>
>  I have made several attempts to run the buildroot program with target set
> to "linux-uclibc" and "linux". It always fails the same way:
>
>  For the "linux-uclibc" target there are no *.o files in .libs directory
> (but it contains libstdc++.a, libstdc++.la, and libstdc++.lai).
>
>  /home/piotr/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ar
> cru libstdc++_pic.a .libs/*.o ../libsupc++/*.o
> /home/piotr/buildroot/build_arm/staging_dir/usr/bin/arm-linux-uclibc-ar:
> .libs/*.o: No such file or directory make[4]: *** [install-exec-local]
> Error 1
>  make[4]: Leaving directory
> `/home/piotr/buildroot/toolchain_build_arm/gcc-3.4.6-final/arm-linux-uclibc
>/libstdc++-v3/src' make[3]: *** [install-am] Error 2
>  make[3]: Leaving directory
> `/home/piotr/buildroot/toolchain_build_arm/gcc-3.4.6-final/arm-linux-uclibc
>/libstdc++-v3/src' make[2]: *** [install-recursive] Error 1
>  make[2]: Leaving directory
> `/home/piotr/buildroot/toolchain_build_arm/gcc-3.4.6-final/arm-linux-uclibc
>/libstdc++-v3' make[1]: *** [install-target-libstdc++-v3] Error 2
>  make[1]: Leaving directory
> `/home/piotr/buildroot/toolchain_build_arm/gcc-3.4.6-final' make: ***
> [/home/piotr/buildroot/toolchain_build_arm/gcc-3.4.6-final/.installed]
> Error 2
>

There is a patch which fixes this in the bug-tracker, 
http://bugs.uclibc.org/view.php?id=1620.
Now, if someone with commit access could be so kind .....

- Atle

  parent reply	other threads:[~2008-01-07 16:09 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
2008-01-07 16:05   ` Piotr Grudzinski
2008-01-07 16:09 ` Atle Nissestad [this message]
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=200801071709.25722.atle@nissestad.no \
    --to=atle@nissestad.no \
    --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