| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
Just wondering which case this covers: +ifeq ($(findstring powerpc,$(shell uname -p)),powerpc) +DESTCPU ?= ppc +else otherwise LGTM |
Sorry, something went wrong.
|
That case covers AIX. |
Sorry, something went wrong.
|
@nodejs/build |
Sorry, something went wrong.
|
Note about the implementation: With regards to host architecture detection there are two other places this is done in the build scripts:
|
Sorry, something went wrong.
|
@mhdawson I've updated the commit so on AIX it defaults to 64-bit as we discussed on the phone. |
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
@jbergstroem just wondering if you can take a quick look and let me know if you have any concerns with this. |
Sorry, something went wrong.
|
I can't claim to know enough of this to stamp it, but since it uses only ?= it seems quite safe to me. However, at least ARM64 is missing: $ uname -m
aarch64 |
Sorry, something went wrong.
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture.
|
Thanks, rebased onto latest master and added aarch64. |
Sorry, something went wrong.
|
ci: https://ci.nodejs.org/job/node-test-pull-request/2614/ overall the changes to the makefile LGTM How was ppc + arm being detected and built correctly before? |
Sorry, something went wrong.
|
sgtm might be time to pull out all of this ARCH and DESTCPU stuff into a script (bash or perl) in tools |
Sorry, something went wrong.
|
@rvagg we could use python's os stuff. Would align well with our build stack. |
Sorry, something went wrong.
|
@jbergstroem sounds good. To clarify though, that shouldn't hold up this PR if the IBM folks agree. @thealphanerd we manually specify both ARCH and DESTCPU in all (?) our build machines so we don't get caught up by this, it's obviously a concern for end-users on any of these platforms, however. |
Sorry, something went wrong.
|
@rvagg we don't manually specify it on all our machines; mainly release-related stuff -- I think we should avoid it where possible since we'd be testing the configure process as well. With that said, in cases we have to, we should obviously override (esp DESTCPU). |
Sorry, something went wrong.
|
LGTM from me as well btw. Just haven't tried all variations of uname. |
Sorry, something went wrong.
|
Looks like we have enough LGTMs to land, will do that now |
Sorry, something went wrong.
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture. PR-URL: #6310 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture. PR-URL: #6310 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture. PR-URL: #6310 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture. PR-URL: #6310 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
`make binary` attempts to auto detect DESTCPU if not set, but was assuming being on an Intel architecture. PR-URL: #6310 Reviewed-By: Johan Bergström <bugs@bergstroem.nu> Reviewed-By: Myles Borins <myles.borins@gmail.com> Reviewed-By: Michael Dawson <michael_dawson@ca.ibm.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
build
Description of change
make binary attempts to auto detect DESTCPU if not set, but was
assuming being on an Intel architecture (i.e. it was checking for x64
and assuming x86 otherwise).