Repository navigation
build will fail if only python3 avaiable #38791
Copy link
Copy link
Closed
Labels
gypIssues and PRs related to GYP and .gyp or .gypi build files.Issues and PRs related to GYP and .gyp or .gypi build files.pythonPRs and issues that require attention from people who are familiar with Python.PRs and issues that require attention from people who are familiar with Python.
Description
Found this on testing gcc-11 docker image.
[251/3367] ACTION postmortem-metadata: gen-postmortem-metadata_7acc03b21ed727c9887fcf4669bc652e
FAILED: gen/debug-support.cc
cd ../../tools/v8_gypfiles; python ../../deps/v8/tools/gen-postmortem-metadata.py ../../out/Release/gen/debug-support.cc ../../out/Release/gen/torque-generated/instance-types.h ../../deps/v8/src/objects/allocation-site.h ../../deps/v8/src/objects/allocation-site-inl.h ../../deps/v8/src/objects/cell.h ../../deps/v8/src/objects/cell-inl.h ../../deps/v8/src/objects/code.h ../../deps/v8/src/objects/code-inl.h ../../deps/v8/src/objects/data-handler.h ../../deps/v8/src/objects/data-handler-inl.h ../../deps/v8/src/objects/descriptor-array.h ../../deps/v8/src/objects/descriptor-array-inl.h ../../deps/v8/src/objects/feedback-cell.h ../../deps/v8/src/objects/feedback-cell-inl.h ../../deps/v8/src/objects/fixed-array.h ../../deps/v8/src/objects/fixed-array-inl.h ../../deps/v8/src/objects/heap-number.h ../../deps/v8/src/objects/heap-number-inl.h ../../deps/v8/src/objects/heap-object.h ../../deps/v8/src/objects/heap-object-inl.h ../../deps/v8/src/objects/instance-type.h ../../deps/v8/src/objects/js-array-buffer.h ../../deps/v8/src/objects/js-array-buffer-inl.h ../../deps/v8/src/objects/js-array.h ../../deps/v8/src/objects/js-array-inl.h ../../deps/v8/src/objects/js-function-inl.h ../../deps/v8/src/objects/js-function.cc ../../deps/v8/src/objects/js-function.h ../../deps/v8/src/objects/js-objects.cc ../../deps/v8/src/objects/js-objects.h ../../deps/v8/src/objects/js-objects-inl.h ../../deps/v8/src/objects/js-promise.h ../../deps/v8/src/objects/js-promise-inl.h ../../deps/v8/src/objects/js-regexp.cc ../../deps/v8/src/objects/js-regexp.h ../../deps/v8/src/objects/js-regexp-inl.h ../../deps/v8/src/objects/js-regexp-string-iterator.h ../../deps/v8/src/objects/js-regexp-string-iterator-inl.h ../../deps/v8/src/objects/map.cc ../../deps/v8/src/objects/map.h ../../deps/v8/src/objects/map-inl.h ../../deps/v8/src/objects/name.h ../../deps/v8/src/objects/name-inl.h ../../deps/v8/src/objects/objects.h ../../deps/v8/src/objects/objects-inl.h ../../deps/v8/src/objects/oddball.h ../../deps/v8/src/objects/oddball-inl.h ../../deps/v8/src/objects/primitive-heap-object.h ../../deps/v8/src/objects/primitive-heap-object-inl.h ../../deps/v8/src/objects/scope-info.h ../../deps/v8/src/objects/scope-info-inl.h ../../deps/v8/src/objects/script.h ../../deps/v8/src/objects/script-inl.h ../../deps/v8/src/objects/shared-function-info.cc ../../deps/v8/src/objects/shared-function-info.h ../../deps/v8/src/objects/shared-function-info-inl.h ../../deps/v8/src/objects/string.cc ../../deps/v8/src/objects/string-comparator.cc ../../deps/v8/src/objects/string-comparator.h ../../deps/v8/src/objects/string.h ../../deps/v8/src/objects/string-inl.h ../../deps/v8/src/objects/struct.h ../../deps/v8/src/objects/struct-inl.h
/bin/sh: 1: python: not foundReactions are currently unavailable
Metadata
Metadata
Assignees
Labels
gypIssues and PRs related to GYP and .gyp or .gypi build files.Issues and PRs related to GYP and .gyp or .gypi build files.pythonPRs and issues that require attention from people who are familiar with Python.PRs and issues that require attention from people who are familiar with Python.
Activity
targos commentedon May 24, 2021
It's because actions that run Python in our gypfiles directly reference the
pythonexecutable:node/tools/v8_gypfiles/v8.gyp
Line 1661 in e9e851f
Maybe we should do something in GYP to expose
sys.executableas a variable?richardlau commentedon May 24, 2021
I believe this is only an issue for building with Ninja. With make our configure scripts write out the path to Python as the
PYTHONmake variable viaconfig.mkbut also create a symbolicpythonlink tosys.executableif it's not the same binary aspythonon the PATH and append the directory containing the link to PATH:node/configure.py
Lines 1952 to 1954 in e9e851f
node/configure.py
Lines 1971 to 1976 in e9e851f
node/configure.py
Lines 1837 to 1868 in e9e851f
(FWIW this is also the reason the V8 CI builds fail when Node.js'
configureis run with Python 3 as the override means#!/usr/bin/env pythonends up pointing to the Python 3 binaryconfigurewas run with instead of the defaultpython.)skys215 commentedon Mar 16, 2022
Am I the only one face the same problem after upgrading macos to 12.3?