Solved www/node fails to build

jbo@

Developer
Hi,

For a few days, my poudriere instance is unable to build www/node:
Code:
ld: error: undefined symbol: RSA_get0_pss_params
>>> referenced by crypto_rsa.cc
>>>               crypto_rsa.o:(node::crypto::GetRsaKeyDetail(node::Environment*, std::__1::shared_ptr<node::crypto::KeyObjectData>, v8::Local<v8::Object>)) in archive /wrkdirs/usr/ports/www/node/work/node-v16.10.0/out/Release/obj.target/libnode.a
c++: error: linker command failed with exit code 1 (use -v to see invocation)

Could anybody shed some light on this? I'd have expected a port like this to build out-of-the-box as there are a lot of dependencies (including www/firefox) consuming it.
I haven't changed anything and I am building with default options.

The full build log can be found here: https://freebsd.binaries.insane.eng...-09-27_12h00m07s/logs/errors/node-16.10.0.log
 
It's always worthwhile to see if the build clusters has the same or similar problems. If there are problems there too then you can be sure it's not an issue on your end. But the latest build for www/node seems to have been successful there: http://beefy16.nyi.freebsd.org/data/130amd64-default/28d5dd624cd7/logs/node-16.10.0.log

I suggest updating your 13.0-RELEASE poudriere jail. It looks to be missing a bunch of security and errata patches. Specifically this one: https://www.freebsd.org/security/advisories/FreeBSD-EN-21:24.libcrypto.asc. That might be the reason why it's failing.
 
It's always worthwhile to see if the build clusters has the same or similar problems. If there are problems there too then you can be sure it's not an issue on your end.
I did that before posting here - should have mentioned that :D


I suggest updating your 13.0-RELEASE poudriere jail. It looks to be missing a bunch of security and errata patches. Specifically this one: https://www.freebsd.org/security/advisories/FreeBSD-EN-21:24.libcrypto.asc. That might be the reason why it's failing.
That was indeed the issue. I updated the poudriere jail and now it builds successfully again :)


Thanks for the help.
 
OFFTOPIC

It's always worthwhile to see if the build clusters has the same or similar problems. ... http://beefy16.nyi.freebsd.org/data/130amd64-default/28d5dd624cd7/logs/node-16.10.0.log
I did that before posting here - should have mentioned that
Lucky those whose ISP is offering IPv6. Without IPv6 support one must settle with https://portsfallout.com and "Report URL:". Maybe I should look for a IPv6 tunnel broker.

Someone has any experience with free providers?
 
Maybe I should look for a IPv6 tunnel broker.

Someone has any experience with free providers?
I've been using an IPv6 tunnel from he.net (https://tunnelbroker.net/) for many years, rarely had issues with it. They'll even provide configuration snippets for use on FreeBSD (although I had to change a couple of things to make it work correctly). My ISP only provides IPv6 if I put my modem in router mode, but I'm using it in bridged mode.
 
Another vote for HE's tunnelbroker, works perfectly here, and with very little overhead.
Surprisingly little overhead I might add. You can pick the location of the exit node and get a free /64 and a /48 if you want it.
 
Back
Top