From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] python-setuptools: Add patch to prevent detecting the host installation
Date: Thu, 22 Aug 2013 08:24:38 -0300 [thread overview]
Message-ID: <5215F4F6.4030701@zacarias.com.ar> (raw)
In-Reply-To: <5215F336.8050106@mind.be>
On 08/22/2013 08:17 AM, Arnout Vandecappelle wrote:
> Markos's patch, or a yet-to-be-created patch that adds $(TARGET_DIR) to
> the PYTHONPATH instead of passing the system's pythonpath?
That's possible too, testing required :)
> Actually I didn't realize the PYTHONPATH setting for the host variant
> was redundant :-) I was only talking about the target.
PYTHONPATH for the target is required because it's sometimes hardcoded
in installed packages unfortunately - i don't recall the exact
combination that triggered it at the moment, or it may have been some
additional python package that i used for testing and never sent
(useless, not interesting) when fixing the shebang and other details.
> But I guess that is a separate patch.
>
> Anyway I'm not sure if the target variant is that relevant, because it
> will not be able to install anything that requires compilation...
Yes, something for someone to up their buildroot cred :)
I'm unsure if we want to encourage the target setuptools, there are
packages that'll install fine, and as you say the compiler ones will
fail miserably.
I'd keep it to avoid unnecessary noise and complaints with a big fat
warning that it's not the buildroot way and it's just for convenience
(and to forget about the target toolchain!).
Regards.
next prev parent reply other threads:[~2013-08-22 11:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 14:25 [Buildroot] [PATCH] python-setuptools: Add patch to prevent detecting the host installation Markos Chandras
2013-08-21 20:49 ` Arnout Vandecappelle
2013-08-22 8:19 ` Yegor Yefremov
2013-08-22 9:07 ` Yegor Yefremov
2013-08-22 9:17 ` Markos Chandras
2013-08-22 9:21 ` Arnout Vandecappelle
2013-08-22 9:18 ` Arnout Vandecappelle
2013-08-22 10:36 ` Yegor Yefremov
2013-08-22 11:12 ` Gustavo Zacarias
2013-08-22 11:17 ` Arnout Vandecappelle
2013-08-22 11:24 ` Gustavo Zacarias [this message]
2013-08-22 20:33 ` Markos Chandras
2013-08-22 20:37 ` 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=5215F4F6.4030701@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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