Uh oh!
There was an error while loading. Please reload this page.
build: enable sse4.2 and ssse3 in zlib - #36693
Conversation
targos
commented
Dec 30, 2020
This is a vendored dependency and we should avoid patching it directly. That said, I'm not sure there's anything to do on our side. In #36678 (comment), compilation is using unsupported GCC 4.8.5 headers, unless I'm misundestanding the directory structure. |
RaisinTen
commented
Dec 30, 2020
That sort of thing ( |
addaleax
commented
Dec 30, 2020
@mscdex This is not “that sort of thing”. |
addaleax
commented
Dec 30, 2020
Yeah, I think that might be good, as @targos mentioned we don’t want to keep floating patches unless we can avoid it. |
2f74dd5 to
23873bfCompareRaisinTen
commented
Dec 31, 2020
@d-mozulyov can you confirm whether this patch works on your system? |
| #if defined(CRC32_SIMD_SSE42_PCLMUL) | ||
| /* Required to make MSVC bot build pass. */ | ||
| // TODO(raisinten): When https://github.com/nodejs/node/pull/33044 lands, | ||
| // remove the next line and add `-msse4.2` to the command line options. |
There was a problem hiding this comment.
Assuming this lands before #33044, a commit should be added to that PR that resolves this TODO.
There was a problem hiding this comment.
CC @richardlau
Please consider adding these options in your PR if you haven't added them already. :)
d-mozulyov
commented
Dec 31, 2020
Hello everyone @RaisinTen, |
RaisinTen
commented
Jan 1, 2021
@d-mozulyov I enabled |
d-mozulyov
commented
Jan 2, 2021
|
RaisinTen
commented
Jan 2, 2021
@d-mozulyov how about now? |
d-mozulyov
commented
Jan 2, 2021
Maybe there are some automated tests so that I don't start the build manually? |
RaisinTen
commented
Jan 2, 2021
I don't think there is any way to automatically test it out currently because there is no official support for |
RaisinTen
commented
Jan 2, 2021
I added the change for this file, does it build now? |
d-mozulyov
commented
Jan 2, 2021
I would like to clarify a few points
P.S. Build error:
|
RaisinTen
commented
Jan 3, 2021
Hmm, that's interesting. What does |
d-mozulyov
commented
Jan 3, 2021
It looks like a rebuild is not being called. An error is displayed immediately: |
RaisinTen
commented
Jan 3, 2021
That's where the problem is. Symlinking it to
Perhaps run a |
Thank you very much for helping to draw attention to the cc symlink. But now the following error is thrown (original master branch). I don't know yet what to do about it. |
RaisinTen
commented
Jan 4, 2021
It can't find the shared standard C++ library. What does |
d-mozulyov
commented
Jan 6, 2021
|
RaisinTen
commented
Jan 6, 2021
ls -l $(g++ -print-file-name=libstdc++.so)Does this print a symlink pointing to |
d-mozulyov
commented
Jan 6, 2021
|
Did you add this earlier in your LD_LIBRARY_PATH=/usr/local/lib64/:$LD_LIBRARY_PATHexport LD_LIBRARY_PATHThe gcc documentation mentions it here: https://gcc.gnu.org/onlinedocs/libstdc++/faq.html#faq.how_to_set_paths |
RaisinTen
commented
Jan 14, 2021
@d-mozulyov is the problem solved? |
d-mozulyov
commented
Feb 4, 2021
Yep |
RaisinTen
commented
Feb 4, 2021
@d-mozulyov awesome! 🎉 |
nodejs-github-bot
commented
Feb 4, 2021
RaisinTen
commented
Feb 4, 2021
targos
commented
Feb 5, 2021
I the problem is solved, we don't need this change, do we ? |
RaisinTen
commented
Feb 5, 2021
@targos I'm not really sure about that. @d-mozulyov could you please confirm that the master branch builds successfully on your machine or is my patch necessary for building Node.js on your tool chain? |
d-mozulyov
commented
Feb 5, 2021
@targos@RaisinTen |
RaisinTen
commented
Feb 6, 2021
@d-mozulyov Thanks for confirming. :) |
Fixes: #36678
Checklist
make -j4 test(UNIX), orvcbuild test(Windows) passes