-
-
Notifications
You must be signed in to change notification settings - Fork 177
fails to build on freebsd 11.1 #390
Comments
@sopparus Could you please copy and paste the full stack-trace here? We need more info to locate the error, but I think this looks familiar: lovell/sharp#873 |
ok, this is full log https://pastebin.com/jT1S4P7r thanks! |
it does, but I dont see any clear solution there? leveldown has also worked fine in the past |
I have absolutely no idea what's going on here so am of no help atm. |
OK @sopparus this is a little confusing. |
I use the precompiled package, and its version node-8.5.0 . |
ok - i'm using a vagrant 11.1 can I take it you are using - https://download.freebsd.org/ftp/releases/ISO-IMAGES/11.1/FreeBSD-11.1-RELEASE-amd64-dvd1.iso ? |
correct |
(Edited)
common.gypi is correct the problem is that the default llvm is being set to 3.8 in build/config.gypi. Simply overriding this with Give the amount of native libs running into this we should consider bumping the defaults to 4.0 in node if possible |
thank you, that work around did the trick. |
Probably this then https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222153 THanks everyone for the help |
Thanks @sopparus That looks like it should work alright - It's basically generating a config.gypi based on the current system rather than the system that node was built on. FWIW I put the reasons why that is happening in this issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220983#c3 If everyone is happy maybe we close this issue? |
Can we add a pre-built node binding to the release? It's trivial to build it using the workaround suggested by @No9 and it will save everyone the trouble. I'll leave leveldown-v2.1.1-node-v57-freebsd-x64.tar.gz here just in case. |
/usr/include/c++/v1/__config:73:2: error: "_LIBCPP_TRIVIAL_PAIR_COPY_CTOR" is no longer supported. use
_LIBCPP_DEPRECATED_ABI_DISABLE_PAIR_TRIVIAL_COPY_CTOR instead
#error "_LIBCPP_TRIVIAL_PAIR_COPY_CTOR" is no longer supported.
^
1 error generated.
The text was updated successfully, but these errors were encountered: