From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 1/1] package/gesftpserver: Fix per-package build without Python
Date: Sun, 11 Jul 2021 19:23:41 +0200 [thread overview]
Message-ID: <875yxgzrvm.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20210626150516.41f5ccd8@windsurf> (Thomas Petazzoni's message of "Sat, 26 Jun 2021 15:05:16 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@bootlin.com> writes:
> On Thu, 24 Jun 2021 14:32:37 +0200
> Andreas Naumann <anaumann@ultratronik.de> wrote:
>> When building per-package in an environment without Python, the gesftpserver
>> configure script dies when looking for Python support.
>> The configure script is happy (doesnt check and wont error out) when being
>> told that Python is not available, so we hack around this by setting the
>> appropriate env variable.
>>
>> Signed-off-by: Andreas Naumann <anaumann@ultratronik.de>
> Thanks, but the issue is not at all related to per-package. In an
> environment without Python, gesftpserver fails to build, even with
> BR2_PER_PACKAGE_DIRECTORIES disabled.
> So I've applied after rewriting the commit log, and adding a comment
> inside the .mk file.
Committed to 2021.02.x and 2021.05.x, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2021-07-11 17:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-24 12:32 [Buildroot] [PATCH v2 1/1] package/gesftpserver: Fix per-package build without Python Andreas Naumann
2021-06-26 13:05 ` Thomas Petazzoni
2021-06-28 8:27 ` Andreas Naumann
2021-07-11 17:23 ` Peter Korsgaard [this message]
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=875yxgzrvm.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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