From: "Rebecca Cran" <rebecca@bsdio.com>
To: devel@edk2.groups.io, pedro.falcato@gmail.com
Cc: Liming Gao <gaoliming@byosoft.com.cn>,
Bob Feng <bob.c.feng@intel.com>,
Yuwei Chen <yuwei.chen@intel.com>, Andrew Fish <afish@apple.com>,
Leif Lindholm <quic_llindhol@quicinc.com>,
Michael D Kinney <michael.d.kinney@intel.com>
Subject: Re: [edk2-devel] [PATCH 1/1] Remove bashisms from edksetup.sh and BaseTools/BuildEnv
Date: Sat, 6 May 2023 13:45:02 -0600 [thread overview]
Message-ID: <3e01cc9e-ac5f-bf4d-0359-adfc1aa21c4b@bsdio.com> (raw)
In-Reply-To: <175CA4E73380D66F.2502@groups.io>
Actually, the python package provides a python command, and python3
provides a python3 command, both of which are Python 3.9.16.
So I no longer need to specify PYTHON_COMMAND.
bcran@maxamd:~/src/uefi/edk2 % /bin/sh
$ . edksetup.sh
Loading previous configuration from
/home/bcran/src/uefi/edk2/Conf/BuildEnv.sh
Using EDK2 in-source Basetools
WORKSPACE: /home/bcran/src/uefi/edk2
EDK_TOOLS_PATH: /home/bcran/src/uefi/edk2/BaseTools
CONF_PATH: /home/bcran/src/uefi/edk2/Conf
$ echo $PYTHON_COMMAND
python3
$ python3 --version
Python 3.9.16
--
Rebecca Cran
On 5/6/23 13:34, Rebecca Cran wrote:
> On 5/6/23 12:34, Pedro Falcato wrote:
>> Did you test this in FreeBSD (and hopefully other BSDs, such as Net)?
>> As far as I know, those don't package a python3 symlink (only
>> python3.{version}).
>>
>> At a glance, the rest of the changes look ok-ish to me though.
>
> I only tested on FreeBSD, where the behavior is the same as before: I
> still need to specify PYTHON_COMMAND=python3.9 .
>
>
next prev parent reply other threads:[~2023-05-06 19:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-06 18:23 [PATCH 1/1] Remove bashisms from edksetup.sh and BaseTools/BuildEnv Rebecca Cran
2023-05-06 18:34 ` [edk2-devel] " Pedro Falcato
2023-05-06 19:34 ` Rebecca Cran
[not found] ` <175CA4E73380D66F.2502@groups.io>
2023-05-06 19:45 ` Rebecca Cran [this message]
2023-05-06 21:48 ` Pedro Falcato
2023-05-07 3:31 ` Rebecca Cran
2023-05-07 3:51 ` Pedro Falcato
2023-05-09 0:53 ` 回复: " gaoliming
2023-05-09 4:28 ` Rebecca Cran
2023-05-10 0:29 ` Rebecca Cran
2023-05-10 0:43 ` Michael D Kinney
2023-05-10 1:02 ` Rebecca Cran
2023-05-10 1:33 ` 回复: " gaoliming
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-list 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=3e01cc9e-ac5f-bf4d-0359-adfc1aa21c4b@bsdio.com \
--to=devel@edk2.groups.io \
/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