From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Wrong compiler path when compiling zlib
Date: Thu, 2 Jan 2014 13:20:26 +0100 [thread overview]
Message-ID: <20140102132026.68c0bb25@skate> (raw)
In-Reply-To: <CA+hj=MpO+iC+YwcHcBsSL7kNMfFAhaV8MZz-mai86tnOD6E3Qw@mail.gmail.com>
Dear Ivan Wagner,
On Thu, 2 Jan 2014 11:37:58 +0100, Ivan Wagner wrote:
> yes you're right it's quite unusual in fact I changed it to little
> endian but I still see the same toolchain paths that aren't pointing
> to the custom pre-installed I've selected.
It is expected that the compiler isn't pointing directly to your
external toolchain. Buildroot compiles a small wrapper around the
external toolchain, in order to pass some appropriate arguments when
the external compiler is called. Therefore it is perfectly normal that
the compiler is called output/host/usr/bin/arm-<something>-gcc. Any
other value would be wrong.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-01-02 12:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-01 22:46 [Buildroot] Wrong compiler path when compiling zlib Ivan Wagner
2014-01-02 4:47 ` Baruch Siach
2014-01-02 9:06 ` Ivan Wagner
2014-01-02 9:19 ` Baruch Siach
2014-01-02 10:08 ` Ivan Wagner
2014-01-02 10:34 ` Baruch Siach
2014-01-02 10:37 ` Ivan Wagner
2014-01-02 11:06 ` Baruch Siach
2014-01-02 11:09 ` Ivan Wagner
2014-01-02 11:17 ` Baruch Siach
2014-01-02 11:35 ` Ivan Wagner
2014-01-02 12:21 ` Thomas Petazzoni
2014-01-02 12:33 ` Ivan Wagner
2014-01-02 12:20 ` Thomas Petazzoni [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=20140102132026.68c0bb25@skate \
--to=thomas.petazzoni@free-electrons.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