Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Philippe Ney <philippe.ney@pardes.ws>
To: buildroot@busybox.net
Subject: [Buildroot] C++ cross compiler]
Date: Thu, 16 Nov 2006 10:44:41 +0100	[thread overview]
Message-ID: <20061116104441.17382885.philippe.ney@pardes.ws> (raw)
In-Reply-To: <29305.82.171.61.116.1163624395.squirrel@webmail.aerende.com>

> Phillipe,
>     If by staging_dir, you mean where the cross compiler
> executables go, there is no arm-linux-uclibc-g++
> in the bin directory where the arm-linux-uclibc-gcc
> executable is.

Yes, where the cross exec goes. This is defined by buildroot in fact.
I just tried to generate a cross-compiler with the same settings as yours
and it worked. Maybe you have to restart from scratch, try others gcc,
binutils, uClibc versions.

As said Mike

  No, there should literally be a directory called
  "buildroot/build_arm_nofpu/staging_dir/bin/"
  (the "build_arm_nofpu" bit depends on your build settings)
  which gets created as part of your buildroot make.

You also could have a look at the gumstix project. They use gcc-3.4.5 and
I guess they generate a C++ cross-compiler.


> 1.  I am using gcc-3.4.2, binutils-2.16.1 and a uClibc
>     snapshot from around Aug. 1, 2006.
> 
> 2.  In toolchain/gcc there is a gcc-uclibc-3.x.mk file.
>     Is this the .mk file you were referring to?

Yes

Philippe

      parent reply	other threads:[~2006-11-16  9:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-15 20:59 [Buildroot] C++ cross compiler] nina.holly at aerende.com
2006-11-16  9:24 ` MikeW
2006-11-16 14:57   ` nina.holly at aerende.com
2006-11-16 16:08     ` MikeW
2006-11-16  9:44 ` Philippe Ney [this message]

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=20061116104441.17382885.philippe.ney@pardes.ws \
    --to=philippe.ney@pardes.ws \
    --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