-
Notifications
You must be signed in to change notification settings - Fork 1
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: fix icu support when target arch != host #12
build: fix icu support when target arch != host #12
Conversation
This is to implement nodejs#7676 (comment) * make `--with-intl=none` the default * Download, verify (md5), unpack ICU's zip if not there * update docs * add a test There's a "list" of URLs being used, but right now only the first is picked up. The logic works something like this: * if there is no directory `deps/icu`, * if no zip file (currently `icu4c-54_1-src.zip`), * download zip file (icu-project.org -> sf.net) * verify the MD5 sum of the zipfile * if bad, print error and exit * unpack the zipfile into `deps/icu` * if `deps/icu` now exists, use it, else fail with help text Also: * refactor some code into tools/configure.d/nodedownload.py * add `intl-none` option for `vcbuild.bat` To rebuild `deps/icu-small` - (not currently checked in) ``` bash tools/icu/prepare-icu-source.sh ``` Also: Reduce space by about 1MB with ICU 54 (over without this patch). Also trims a few other source files, but only conditional on the exact ICU version used. This is to future-proof - a file that is unneeded now may be needed in future ICUs.
I haven't tested cross compiling for ia32 on a x64 host on Windows, and I haven't tested cross-compiling for x64 on a ia32 host on any system. The only cross-compilation configurations I have tested so far are target == ia32 && host == x64 on MacOS X and Linux. I'll keep you posted when I have some time to test more configurations. |
@misterdjules first, thanks for the report and creating the PR. I don't think it can fix exactly that way, but I will take a look. |
(work in progress - attempt to add dummy `#host` toolset remapping to `icutools`)
@misterdjules I really don't understand this or why your patch 'fixes' it. |
Also I note that |
(work in progress - attempt to add dummy `#host` toolset remapping to `icutools`)
@srl295 Indeed, the error message doesn't make sense to me too, and if I rerun the configure command within your branch, I get the error message that I would expect:
I don't know why I got the error message that mentions Did you run this command on your machine? If so, what error message do you get? |
@misterdjules yes I get the same message. I set up a new branch https://github.com/srl295/node/tree/srl-v0.12-FixToolsetAgain for just this, and reverted my |
also see nodejs#7676 (comment) for the previous
|
12c8fca
to
ab52511
Compare
(work in progress - attempt to add dummy `#host` toolset remapping to `icutools`)
(work in progress - attempt to add dummy `#host` toolset remapping to `icutools`)
8c4b059
to
b048092
Compare
Without this change, I get the following error when running configure with
--dest-cpu=ia32
on a x64 system:The change in this PR fixes it, but I'm not sure it's the proper way to do it.