From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gpsd: fix Python-related build failure
Date: Wed, 22 Aug 2012 20:06:15 +0200 [thread overview]
Message-ID: <20120822200615.42118e87@skate> (raw)
In-Reply-To: <CAHt8ZCPRsyLfCKQfOfa5LQ3qeX22_3UgLJAXH0YfeGSb1sQ8-A@mail.gmail.com>
Le Wed, 22 Aug 2012 09:26:06 +0100,
Simon Dawson <spdawson@gmail.com> a ?crit :
> > I guess the real problem that we have to address here is why scons uses
> > the interpreter from the distribution and not the buildroot-generated one.
> >
> > I guess, we could just make scons depends on host-python and force the
> > $(SCONS) variable as "$(HOST_DIR)/usr/bin/python
> > $(HOST_DIR)/usr/bin/scons ?"
>
> This sounds to me like a good idea. I had tried to avoid the
> host-python dependency, which was in fact present in an earlier
> incarnation of the gpsd version bump patch. But it looks like it might
> be the cleanest way of resolving the present issue.
If we could avoid the host-python dependency, it would be great. My
understanding is that the SConstruct needs JSON just to generate one
file. Maybe we could simply integrate a pre-generated version as a
patch. But maybe it's too hackish, and we should just go ahead and add
host-python as a dependency of scons, so that a well-known version of
Python gets built.
Best regards,
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-08-22 18:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-21 11:31 [Buildroot] [PATCH] gpsd: fix Python-related build failure spdawson at gmail.com
2012-08-22 8:07 ` Maxime Ripard
2012-08-22 8:26 ` Simon Dawson
2012-08-22 18:06 ` Thomas Petazzoni [this message]
2012-08-24 7:59 ` [Buildroot] [PATCH] gpsd: Fix lacking simplejson module error at build Maxime Ripard
2012-08-24 10:43 ` Thomas Petazzoni
2012-08-24 21:43 ` 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=20120822200615.42118e87@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.