From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt tribulations take 2
Date: Sun, 15 Jul 2012 01:05:42 +0200 [thread overview]
Message-ID: <20120715010542.1a23ba0f@skate> (raw)
In-Reply-To: <CALo-6+hSrFrqua1s48qzYn9J8qF0F6=zCpgfbguO2hf3VmqeOQ@mail.gmail.com>
Le Sat, 14 Jul 2012 15:00:18 -0700,
Charles Krinke <charles.krinke@gmail.com> a ?crit :
> You were right as usual. It was an environment variable. It was
> QMAKESPEC which was set by my installation of the TI SDK a week ago. I
> should have checked my .bashrc after installing the SDK, but I did
> not expect any environment changes as a result of installing a
> toolchain and u-boot source.
Then we should probably unset this environment variable in the main
Makefile. It seems like a lot of environment variables are causing
various issues in the build. Is there any way to simply unset all
environments variables, except the few we are actually interested in?
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-07-14 23:05 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-13 13:51 [Buildroot] Qt tribulations take 2 Charles Krinke
2012-07-13 14:55 ` Thomas Petazzoni
2012-07-13 15:41 ` Charles Krinke
2012-07-14 16:25 ` Julian Lunz
2012-07-14 22:00 ` Charles Krinke
2012-07-14 23:05 ` Thomas Petazzoni [this message]
2012-07-15 10:33 ` Arnout Vandecappelle
2012-07-15 10:38 ` Thomas Petazzoni
2012-08-16 17:28 ` Stephan Hoffmann
2012-08-17 11:29 ` Thomas Petazzoni
2012-07-14 23:12 ` Arnout Vandecappelle
2012-07-14 20:56 ` Arnout Vandecappelle
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=20120715010542.1a23ba0f@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.