From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Build error when trying to build the py-smbus package of i2c-tools
Date: Fri, 21 Jun 2013 14:48:55 +0200 [thread overview]
Message-ID: <20130621144855.013f0222@skate> (raw)
In-Reply-To: <4E062DFADC6E8142AA8EE9D214BA0C50E403D5@NB-EX-MBX01.diasemi.com>
Dear Thomas Weininger,
On Fri, 21 Jun 2013 12:37:33 +0000, Thomas Weininger wrote:
> So CC_FOR_BUILD and GCC_FOR_BUILD point to /usr/bin/gcc. Couldn't be that the source of the errors?
> But when this is wrong, why does the rest of i2c-tools build successfully?
CC_FOR_BUILD and GCC_FOR_BUILD are correct. As their name suggest,
those variables should point to the compiler that allows to build
things for the /build/ machine, i.e the native compiler.
CC => compiler to build things for the host machine
CC_FOR_BUILD => compiler to build things for the build machine
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-06-21 12:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 7:18 [Buildroot] Build error when trying to build the py-smbus package of i2c-tools Thomas Weininger
2013-06-20 7:57 ` Thomas Petazzoni
2013-06-20 9:30 ` Thomas Weininger
2013-06-20 16:25 ` Arnout Vandecappelle
2013-06-21 9:28 ` Thomas Weininger
2013-06-21 9:49 ` Arnout Vandecappelle
2013-06-21 10:31 ` Thomas Weininger
2013-06-21 10:48 ` Arnout Vandecappelle
2013-06-21 12:06 ` Thomas Weininger
2013-06-21 12:37 ` Thomas Weininger
2013-06-21 12:48 ` 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=20130621144855.013f0222@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