Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Build from source error on Catalina #30276

Closed
glevanov opened this issue Nov 6, 2019 · 6 comments
Closed

Build from source error on Catalina #30276

glevanov opened this issue Nov 6, 2019 · 6 comments
Labels
macos Issues and PRs related to the macOS platform / OSX. python PRs and issues that require attention from people who are familiar with Python.

Comments

@glevanov
Copy link

glevanov commented Nov 6, 2019

  • Version: v10.16.3
  • Platform: Darwin Grigoriys-MacBook-Pro.local 19.0.0 Darwin Kernel Version 19.0.0: Thu Oct 17 16:17:15 PDT 2019; root:xnu-6153.41.3~29/RELEASE_X86_64 x86_64

The Error

I was building Node binary for Code+Learn meetup. I was following the official guide.

The build passed without errors. However when I laucned make test-only, I got the following messages in output:

make[1]: *** [jstest] Error 1
make: *** [test-only] Error 2

What I did before

First I encountered issues with ./configure:

grigoriylevanov (master) node $ ./configure
Node configure: Found Python 3.7.4...
INFO: Using floating patch "tools/icu/patches/64/source/common/putil.cpp" from "tools/icu"
INFO: Using floating patch "tools/icu/patches/64/source/i18n/dtptngen.cpp" from "tools/icu"
No receipt for 'com.apple.pkg.DeveloperToolsCLILeo' found at '/'.
No receipt for 'com.apple.pkg.DeveloperToolsCLI' found at '/'.
gyp: No Xcode or CLT version detected!
Error running GYP

I've followed the guide for node-gyp issues with xcode in Catalina and passed the acid test (as descibed here), however it did not help with build.

Just in case, this is my acid test results:

grigoriylevanov (master *) node $ /usr/sbin/pkgutil --packages | grep CL
com.apple.pkg.CLTools_Executables
com.apple.pkg.CLTools_SDK_macOS1015
com.apple.pkg.CLTools_SDK_macOS1014
com.apple.pkg.CLTools_macOS_SDK

grigoriylevanov (master *) node $ /usr/sbin/pkgutil --pkg-info com.apple.pkg.CLTools_Executables
package-id: com.apple.pkg.CLTools_Executables
version: 11.0.0.0.1.1567737322
volume: /
location: /
install-time: 1572944110
groups: com.apple.FindSystemFiles.pkg-group 

I also have a different python version (2.7, not 3.7):

grigoriylevanov (master *) node $ python -V
Python 2.7.16

Our chat came up with the following workaround - if we comment out the following in ./configure, config and build pass without errors.

test ${TRAVIS} && exec python "$0" "$@"  # workaround for pyenv on Travis CI
#which python3.8 >/dev/null && exec python3.8 "$0" "$@"
#which python3.7 >/dev/null && exec python3.7 "$0" "$@"
#which python3.6 >/dev/null && exec python3.6 "$0" "$@"
#which python3.5 >/dev/null && exec python3.5 "$0" "$@"
which python2.7 >/dev/null && exec python2.7 "$0" "$@"
exec python "$0" "$@"
''' "$0" "$@"
grigoriylevanov (master) node $ ./configure
Node configure: Found Python 2.7.16...
INFO: Using floating patch "tools/icu/patches/64/source/common/putil.cpp" from "tools/icu"
INFO: Using floating patch "tools/icu/patches/64/source/i18n/dtptngen.cpp" from "tools/icu"
INFO: configure completed successfully

I've also attached full log of make test-only output: log.txt.

I am building from the following:

grigoriylevanov (master *) node $ git log
commit 1f2fdc9538f2ee9d9fad68137798c49113e96274 (HEAD -> master, origin/master, origin/HEAD)

@legendecas
Copy link
Member

I think this would be a duplicate of #30129. python2 ./configure should work for now.

@ChALkeR
Copy link
Member

ChALkeR commented Nov 6, 2019

@glevanov could you confirm that it works now?

@cclauss cclauss added macos Issues and PRs related to the macOS platform / OSX. python PRs and issues that require attention from people who are familiar with Python. labels Nov 6, 2019
@ChALkeR
Copy link
Member

ChALkeR commented Nov 6, 2019

@glevanov confirmed that ./configure now works on Python 3, but the tests results were unchanged and still have timeouts.

dgram timeouts looks similar to #30030 (comment).

EPIPE looks like the flaky test from #29341.

@BridgeAR is there anything else here?

@glevanov
Copy link
Author

glevanov commented Nov 6, 2019

Updated logs attached

configure.txt
make.txt
test-only.txt

@ChALkeR
Copy link
Member

ChALkeR commented Nov 6, 2019

@glevanov Thanks!

I don't think there is anything new here on top of #30030 (comment) and #29341 now.

@bnoordhuis
Copy link
Member

I'll go ahead and close this out then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
macos Issues and PRs related to the macOS platform / OSX. python PRs and issues that require attention from people who are familiar with Python.
Projects
None yet
Development

No branches or pull requests

5 participants