All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-09
Date: Thu, 11 Aug 2016 22:23:54 +0200	[thread overview]
Message-ID: <20160811222354.754b418d@free-electrons.com> (raw)
In-Reply-To: <20160811200026.GA5812@free.fr>

Hello,

On Thu, 11 Aug 2016 22:00:26 +0200, Yann E. MORIN wrote:

> If Xen can be told what python to use, then that's easy (e.g.:
> --with-python=python2 or whatever else...)

Please try to find a solution like this: environment variable,
configuration option, etc. If it doesn't exist, please add it.

> However, if you can't tell Xen what python to use, then this is a bit
> more involved.
> 
> See how it was solved for example for qt5webkit:
> 
>     package/qt5webkit: needs host-python
> 
>     The Qt5Webkit build system hard-codes calls to 'python', but only really
>     supports python2.
> 
>     We fix that similarly as we did in nodejs, by adding a python->python2
>     symlink early in the PATH when configuring/building Qt5Webkit, and
>     adding host-python in the dependency list.
> 
>     [--SNIP--]
> 
> This is commit ac16793eaaabfced0312420759e3a66cdaa1ea8e and you can get
> some inspiration from it.

I really *hate* this solution, and I will actively discourage anyone to
use it.

> Thomas, we now have a few packages that need this hack. Should we try to
> move those hacks into the pkg infra (obviously not for 2016.08)?

As far as I know there are only two such packages today, so clearly not
enough to move those hacks to the pkg infra.

Plus moving this to the pkg infra is making the usage of this hack
easier, which is exactly the opposite of what I want. The more painful
it can be to use this hack, the better, as it will encourage people to
find real solutions.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-08-11 20:23 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-10  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-09 Thomas Petazzoni
2016-08-10 14:14 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-10 19:36   ` Waldemar Brodkorb
2016-08-10 20:30     ` Thomas Petazzoni
2016-08-10 22:21   ` Alistair Francis
2016-08-11 20:00     ` Yann E. MORIN
2016-08-11 20:23       ` Thomas Petazzoni [this message]
2016-08-12 22:33         ` Alistair Francis
2016-08-12  9:31   ` Jörg Krause
2016-08-17  2:27     ` Matthew Weber
2016-08-17  9:20       ` Yann E. MORIN
2016-08-13 21:14   ` Vivien Didelot
2016-08-13 21:55     ` Yann E. MORIN
2016-08-13 22:14       ` Yann E. MORIN
2016-08-14  0:17         ` Arnout Vandecappelle
2016-08-14  0:37           ` Yann E. MORIN

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=20160811222354.754b418d@free-electrons.com \
    --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.