| Summary: | host-nodejs 10.15.3 package fail to build | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Mirko Günther <mirko.guenther> |
| Component: | Other | Assignee: | Martin <martin> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | buildroot |
| Priority: | P5 | ||
| Version: | 2019.08 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Host: | Target: | ||
| Build: | |||
|
Description
Mirko Günther
2019-09-11 09:50:13 UTC
We are seeing the same problem in the autobuilders (on one machine): http://autobuild.buildroot.net/results/57d/57d3f2fb2c0303c338b03a407420b1e1740ccb9a/build-end.log. Looks like it gets linked with our host-openssl, but the RPATH is missing... We try to fix this by explicitly adding the rpath in nodejs.mk (cfr. commit 2ebc2219d5716f81789f29dcbb6b05d0c9d886dd), but unfortunately that is apparently too late because torque does get used during the build of host-nodejs itself... Short of fixing the horrible nodejs build system, I can't think of an easy way to get around this issue :-/ Oh, hang on: the call to torque seems to set LD_LIBRARY_PATH to $(HOST_NODEJS_BUILDDIR)/out/Release/lib.host. So we can copy/symlink the openssl libraries to that directory before the build... I have submitted a fix at https://patchwork.ozlabs.org/patch/1201814/ |