Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 12211] host-nodejs 10.15.3 package fail to build
Date: Tue, 17 Sep 2019 20:02:10 +0000	[thread overview]
Message-ID: <bug-12211-163-1QKJXLHCS0@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-12211-163@https.bugs.busybox.net/>

https://bugs.busybox.net/show_bug.cgi?id=12211

--- Comment #2 from Arnout Vandecappelle <arnout@mind.be> ---
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...

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2019-09-17 20:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-11  9:50 [Buildroot] [Bug 12211] New: host-nodejs 10.15.3 package fail to build bugzilla at busybox.net
2019-09-11 13:26 ` [Buildroot] [Bug 12211] " bugzilla at busybox.net
2019-09-11 13:26 ` bugzilla at busybox.net
2019-09-17 20:02 ` bugzilla at busybox.net [this message]
2019-11-27 20:38 ` bugzilla at busybox.net
2019-11-28 19:41 ` bugzilla at busybox.net
2019-11-28 19:41 ` bugzilla at busybox.net

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-12211-163-1QKJXLHCS0@https.bugs.busybox.net/ \
    --to=bugzilla@busybox.net \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox