public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Rebecca Cran" <rebecca@bsdio.com>
To: Pedro Falcato <pedro.falcato@gmail.com>, devel@edk2.groups.io
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 21:31:54 -0600	[thread overview]
Message-ID: <7e3cccac-ade2-7a5c-29e0-50c080a31abe@bsdio.com> (raw)
In-Reply-To: <CAKbZUD2mEetmDK3p4DZcMx4FFsP99Udt0mzzzrBL=BbYKn295Q@mail.gmail.com>

On 5/6/23 15:48, Pedro Falcato wrote:
>
> My local installations of Net (latest stable) and FreeBSD (13.1 with a
> hacked-up kernel) do not have a python3 symlink.
>
> I'm slightly worried that this breaks something. I know requiring
> whereis isn't ideal, but I'm fairly sure it did handle this situation?

I uninstalled the python and python3 packages, leaving only python39.

I got the following results on edk2 master:


[bcran@maxamd ~/src/uefi/edk2]$ whereis python3
python3:

[bcran@maxamd ~/src/uefi/edk2]$ ls /usr/local/bin | grep python

python3.9

python3.9-config

[bcran@maxamd ~/src/uefi/edk2]$ . edksetup.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


[bcran@maxamd ~/src/uefi/edk2]$ echo $PYTHON_COMMAND

[bcran@maxamd ~/src/uefi/edk2]$ gmake -C BaseTools/ -j16
gmake: Entering directory '/usr/home/bcran/src/uefi/edk2/BaseTools'
gmake -C Source/C
gmake -C Source/Python
gmake[1]: Entering directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/C'
gmake[1]: Entering directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/Python'
gmake[1]: Nothing to be done for 'all'.
gmake[1]: Leaving directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/Python'
Attempting to detect HOST_ARCH from 'uname -m': amd64
Detected HOST_ARCH of X64 using uname.
mkdir -p .
mkdir ./libs
mkdir ./bin
gmake -C VfrCompile VfrLexer.h
gmake -C Common
gmake[2]: Entering directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/C/VfrCompile'
gmake[2]: Entering directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/C/Common'

.....

Finished building BaseTools C Tools with HOST_ARCH=X64
gmake[1]: Leaving directory 
'/usr/home/bcran/src/uefi/edk2/BaseTools/Source/C'
gmake -C Tests
gmake[1]: Entering directory '/usr/home/bcran/src/uefi/edk2/BaseTools/Tests'
/bin/sh: python: not found
gmake[1]: *** [GNUmakefile:11: test] Error 127
gmake[1]: Leaving directory '/usr/home/bcran/src/uefi/edk2/BaseTools/Tests'
gmake: *** [GNUmakefile:19: Tests] Error 2
gmake: Leaving directory '/usr/home/bcran/src/uefi/edk2/BaseTools'
...

[bcran@maxamd ~/src/uefi/edk2]$ build -p OvmfPkg/OvmfPkgX64.dsc -a X64 
-t GCC -b RELEASE
/home/bcran/src/uefi/edk2/BaseTools/BinWrappers/PosixLike/build: line 
14: exec: python: not found


-- 

Rebecca Cran


  reply	other threads:[~2023-05-07  3:31 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
2023-05-06 21:48       ` Pedro Falcato
2023-05-07  3:31         ` Rebecca Cran [this message]
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=7e3cccac-ade2-7a5c-29e0-50c080a31abe@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