Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] C++ cross compiler]
Date: Thu, 16 Nov 2006 16:08:42 +0000 (UTC)	[thread overview]
Message-ID: <loom.20061116T165730-420@post.gmane.org> (raw)
In-Reply-To: 13882.82.171.61.116.1163689078.squirrel@webmail.aerende.com

 <nina.holly@...> writes:

> 
> 
> > 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.
> > What is the directory path in your system to what you call
> > "where the cross compiler executables go" ?
> 
> That is /usr/local/arm/release-3.4.2.  In this directory there are
> the directories:
> 
> arm-linux-uclibc
> bin
> bin-ccache
> include
> info
> lib
> libexec
> man
> usr
> 
> arm-linux-uclibc has the directories:
> 
> bin
> target_utils
> 
> which just have executables such as ar, as, gcc, ld, gdbserver, etc.
> 
> /usr/local/arm/release-3.4.2/bin has:
> 
> arm-linux-gcc-3.4.2-?arm-linux-uclibc-gcc-3.4.2
> 
> etc.
> 
> but no arm-linux-g++
> 
> Nina
> 
You should *not* set your staging_dir to be /usr/local ... !

The reason you do not see a C++ compiler there is because you
can only install programs there as root.
The other compiler files you see there must be left from some
earlier installation, or must have permissions that allow overwriting.

But before you change the permissions, read further !

For one thing, the staging_dir is used during the build process
of buildroot to store not only the toolchain files, but acts
as the holding area for the files immediately prior to constructing
the root filesystem. As such it will contain other files which are
used in the build process but will not be present on the root filesystem,
such as source headers and static libraries.

SO the staging_dir setting in the menuconfig should NOT be set
to /usr/local...anything, it should preferably be left as
the default value, which causes it to be in the place I said before.

If you want to use the toolchain you have built with buildroot,
follow the instructions in the buildroot documents and use the
compilers within staging_dir/bin.

You can always make some symbolic links to the tools for convenience.

Hope that gets you going again.

Regards,

MikeW

  reply	other threads:[~2006-11-16 16:08 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 [this message]
2006-11-16  9:44 ` Philippe Ney

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=loom.20061116T165730-420@post.gmane.org \
    --to=mw_phil@yahoo.co.uk \
    --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