From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] BUG: Buildroot build environment is messing up with host Python scripts
Date: Mon, 17 May 2021 13:52:42 +0200 [thread overview]
Message-ID: <20210517115242.GT2506@scaer> (raw)
In-Reply-To: <YKJMZtZU0kyfknpZ@smile.fi.intel.com>
Andy, All,
On 2021-05-17 13:58 +0300, Andy Shevchenko spake thusly:
> I have a very long time ago established a script that makes adaptive proxy for
> Git and SSH. This script is written in Python and has the following shebang:
>
> #!/usr/bin/env python3
>
> When Buildroot tries to download sources from a Git repository, the above
> mentioned script is being called to determine if proxy is needed and what its
> configuration. Unfortunately it seems that Buildroot build environment somehow
> messed up with host (!) one and necessary modules for that script to work can't
> be found. Note, the same script is working nicely with host tools (Git, SSH),
> hence there is no issues on the host side.
>
> Changing shebang to be
>
> #!/usr/bin/python3
>
> works around the problem, but the root cause is somewhere in the Buildroot.
> We must not require to change everything user have on the host (!) side to
> build the Buildroot. It's kinds show stopper to me. Any suggestion how to fix
> this quite annoying bug?
This is not really a bug per-se, and this behaviour has existed since at
least July 2014, with commit 95a572282e (pkg-infra: move the git download
helper to a script), since then the git download is done with the extra
environment defined in EXTRA_ENV, and namely:
EXTRA_ENV = PATH=$(BR_PATH) [....]
and where:
BR_PATH = "$(HOST_DIR)/bin:$(HOST_DIR)/sbin:$(PATH)"
So, this is not a new behaviour in 2021.02, but most probably you
previously did not have host-python3 built as part of your
configuraiton, and now it is. And then, it takes precendence over the
system python3.
I don't see a easy way around, though...
But without the actual error you are seeing, it is impossible to suggest
further tracks of investigation: is the missing stuff a built-in module
of python, or is it a external one?
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2021-05-17 11:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 10:58 [Buildroot] BUG: Buildroot build environment is messing up with host Python scripts Andy Shevchenko
2021-05-17 11:52 ` Yann E. MORIN [this message]
2021-05-17 14:43 ` Andy Shevchenko
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=20210517115242.GT2506@scaer \
--to=yann.morin.1998@free.fr \
--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