Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: buildroot@busybox.net
Subject: [Buildroot] BUG: Buildroot build environment is messing up with host Python scripts
Date: Mon, 17 May 2021 13:58:46 +0300	[thread overview]
Message-ID: <YKJMZtZU0kyfknpZ@smile.fi.intel.com> (raw)

Hi!

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?

Buildroot source code tag: 2021.02.1

-- 
With Best Regards,
Andy Shevchenko

             reply	other threads:[~2021-05-17 10:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17 10:58 Andy Shevchenko [this message]
2021-05-17 11:52 ` [Buildroot] BUG: Buildroot build environment is messing up with host Python scripts Yann E. MORIN
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=YKJMZtZU0kyfknpZ@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.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