-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
nodejs 15.6.0 #174
nodejs 15.6.0 #174
Conversation
Hi! This is the friendly automated conda-forge-linting service. I just wanted to let you know that I linted all conda-recipes in your PR ( |
@conda-forge-admin, rerender |
Hi! This is the friendly automated conda-forge-webservice. |
v8 is built twice when cross-compiling, but with the same target destination but the destination is the same for both builds, causing a conflict Patch puts shared intermediates in the per-toolchain subdirectories, resolving the conflict
might be relevant to recent change in timeout
Got past the ninja conflict with a patch, but now failing with:
The issue being that torque apparently needs to be built for both the host and target, which complicates things as dependencies must be linked from both the host and build prefixes. |
btw, I think it's okay to merge these to clear the backlog of releases and finish fixing arm in a later PR. Is that okay? |
You might need to patch in https://github.com/nodejs/node/pull/37444/files |
- upstream patch for LDFLAGS_host - add library dependencies to build env as well, since they are needed for both the host and target arch
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yay! Team effort. LGTM.
Checklist
0
(if the version changed)conda-smithy
(Use the phrase@conda-forge-admin, please rerender
in a comment in this PR for automated rerendering)