From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Qt tribulations take 2
Date: Sun, 15 Jul 2012 12:38:54 +0200 [thread overview]
Message-ID: <20120715123854.3d6c11f1@skate> (raw)
In-Reply-To: <50029C65.9010004@mind.be>
Le Sun, 15 Jul 2012 12:33:09 +0200,
Arnout Vandecappelle <arnout@mind.be> a ?crit :
> We could define MAKE as env -i $(MAKE), but there are some environment
> variables that are passed to sub-makes that you loose this way. Maybe
> better is to define SHELL as env -i sh, but that could have huge side
> effects...
Hm, ok.
> But maybe we shouldn't exaggerate here. Putting a QMAKESPEC in your
> environment would make any qt build fail, so it's not really a
> buildroot problem. Maybe a better idea is to put in the documentation
> that the safe way is to use 'env -i make' to start a build...
Well, there are already many other environment variables that may break
the build and that we are either checking in
support/dependencies/dependencies.sh, or unsetting in main Makefile.
Shouldn't we do the same for QMAKESPEC?
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-15 10:38 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
2012-07-15 10:33 ` Arnout Vandecappelle
2012-07-15 10:38 ` Thomas Petazzoni [this message]
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=20120715123854.3d6c11f1@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