From: MikeW <mw_phil@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Boost package settings for using cross-compiler ?
Date: Wed, 22 Nov 2006 08:55:14 +0000 (UTC) [thread overview]
Message-ID: <loom.20061122T094835-755@post.gmane.org> (raw)
In-Reply-To: 200611212112.23510.claus.klein@arcormail.de
Claus Klein <claus.klein@...> writes:
>
> Hi,
>
> we use boost with ppc crosscompiler, here is my buildroot package.
>
> Sure, its depend an bjam installed on host, the buildroot C++ toolchain,
theading, zlib, ....
> Realy, a big package for an embedded device
>
> Check the boost configuration in boost.mk!
>
> Regards,
> claus
>
Thanks - I worked around this in my own boost.mk by putting
GCC_ROOT_DIRECTORY (why not _DIR ??) =$(STAGING_DIR)/arm-linux-xxx
within my "$(MAKE) ...<here!>.... all" target command line.
This then allows the Buildroot tools to alias the native gcc tools
without any prefixes. Shame that Boost's own makefile doesn't use CC.
Just have to solve to toolchain EABI version problem now :(
Regards,
Mike
prev parent reply other threads:[~2006-11-22 8:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 15:46 [Buildroot] Boost package settings for using cross-compiler ? MikeW
2006-11-21 20:12 ` Claus Klein
2006-11-22 8:55 ` MikeW [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=loom.20061122T094835-755@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