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:21:21 +0100 [thread overview]
Message-ID: <20140102132121.02090747@skate> (raw)
In-Reply-To: <CA+hj=MrgJn9phMDkgdZrCuT=BumpmmW2EH6VnWBqRzYSP-6Uig@mail.gmail.com>
Dear Ivan Wagner,
On Thu, 2 Jan 2014 12:35:00 +0100, Ivan Wagner wrote:
> I think I found out something. At the moment I was only interested in
> trying to cross-compile qt5 for the ARM arch. So what I've done is to
> create a basic buildroot configuration where I selected the external
> toolchain, basic packages and qt5. But then I directly execute "make
> qt5base-build" and at this stage toolchain-external stuff doesn't get
> executed. That's why I don't see any symlinks.
> If I simply run "make" then the toolchain-external is executed.
Correct. We currently don't have a dependency on all packages to the
toolchain. There are pending patches to fix this.
In the mean time, unless you know in details the Buildroot internals,
you should only do simple "make" commands.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-01-02 12:21 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 [this message]
2014-01-02 12:33 ` Ivan Wagner
2014-01-02 12:20 ` Thomas Petazzoni
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=20140102132121.02090747@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