-
-
Notifications
You must be signed in to change notification settings - Fork 8k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
[Bug] nodejs on FreeBSD may need to be patched #900
Comments
That definitely seems way out of scope for |
I sent a issue ticket here nodejs/node#3716 hope we can find a good way to figure it out! |
BTW, clang LLVM is really fast! 👍 Compilation time spent by clang LLVM:
Compilation time spent by clang GCC:
|
@PeterDaveHello as a separate issue/PR, could you look into using the faster approach on all compilations, via feature detection? If we can speed up source compilation, "build from source" tests might not time out, and then I could support building everything from source :-D |
@ljharb what do you mean all compilations actually? All versions of nodejs? Maybe we can open another issue ticket to discuss with that, I'll be happy to help in my capacity. |
BTW,
and v0.11 has similar problem as v0.12 |
@PeterDaveHello yes - if clang LLVM is that much faster than gcc, then we should build with that whenever possible on every platform for every version |
Okay, #902 |
This may be a hard work, I hope not.
FreeBSD version via
uname -a
:nvm version:
I found that I cannot do
$ nvm install 0.12
on FreeBSD 10.1 amd64 with success, and the error messages came from compiler, both clang LLVM or gcc will have the same problem, and this is not nvm's problem but nvm looks to support FreeBSD in the codes:https://github.com/creationix/nvm/blob/master/nvm.sh#L936
https://github.com/creationix/nvm/blob/master/nvm.sh#L1230-L1233
So I think we should do something to work around.
The error message:
I remember that I installed it from ports and pkg with success before, so I copied the patch from FreeBSD's ports system
(https://www.freshports.org/www/node/files/patch-deps_v8_src_base_platform_platform-posix.cc)
Apply the patches:
After the patches applied, there is no problem anymore!
The text was updated successfully, but these errors were encountered: