Repository navigation
aarch64 and arm64 inconsistencies #5175
Description
Activity
I don't mind unifying it a little like we do for x86/ia32 (although even there we're not fully unified thanks mainly to gyp).
@jbergstroem as an aside: both
ARCHandDESTCPUare passed for theiojs+releaseJenkins job which is why we need to have them explicitly set on the release machines, otherwise it comes out asARCH="" DESTCPU=""and inMakefilethat's read as those variables being set and not up for auto detection. xgene-3 missing both of these env vars lead to failure because Jenkins is configured to use them (which I prefer fwiw).@rvagg I would personally prefer using them only if set so we can fall back on defaults but don't have a strong opinion about it. Don't break what works (like I did last time), I guess.
- added a commit that references this issue
on Feb 23, 2016 - added 3 commits that reference this issue
on Mar 1, 2016
./configurecurrently sets host/target_arch asarm64whereasMakefilewill treat it asaarch64(uname -sdoesn't match anything). Suggesting we give Makefile a similar treatment?/cc @nodejs/build