From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH/next/RFC 1/1] package/nodejs: use host-libopenssl
Date: Tue, 21 Aug 2018 00:00:10 +0200 [thread overview]
Message-ID: <20180821000010.3d93612c@windsurf> (raw)
In-Reply-To: <20180819165158.25255-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 19 Aug 2018 18:51:58 +0200, Bernd Kuhls wrote:
> host-nodejs is configured to build openssl by using its included openssl
> source code which is based on openssl 1.0.2. If host-libopenssl was
> already built its header files are being picked up during host-nodejs
> build, this was verified by adding debug code to
> $(HOST_DIR)/include/openssl/opensslv.h.
>
> This situation was not a problem as long as host-libopenssl was the
> same version than the openssl code included in nodejs.
>
> Some code in host-nodejs-8.11.4/src/node_crypto.cc is guarded by
>
> #if OPENSSL_VERSION_NUMBER < 0x10100000L
>
> to be used only with openssl 1.0.x.
>
> This leads to problems if host-libopenssl 1.1.x was built before. Due
> to the usage of its header files some code in node_crypto.cc is not
> built leading to many linking errors later on, for example:
>
> node_crypto.cc:(.text+0x1a1): undefined reference to `DH_get0_pqg'
>
> When the nodejs package originally was added to buildroot back in
> March 2013:
> https://git.buildroot.net/buildroot/commit/?id=b31bc7d4387095091a109eb879464d54d37a5eab
>
> We did not have a host-libopenssl package back then, it was added one
> month later:
> https://git.buildroot.net/buildroot/commit/?id=7842789cb539b6b64d61b03f5c8dbe6813f01da7
>
> To fix the problem we use host-libopenssl for host-nodejs.
> By using host-libopenssl the build time of nodejs is reduced by ~15s.
>
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/nodejs/nodejs.mk | 9 ++++-----
> 1 file changed, 4 insertions(+), 5 deletions(-)
Applied to next, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin (formerly Free Electrons)
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2018-08-20 22:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 16:51 [Buildroot] [PATCH/next/RFC 1/1] package/nodejs: use host-libopenssl Bernd Kuhls
2018-08-20 21:13 ` Yann E. MORIN
2018-08-20 22:00 ` Thomas Petazzoni [this message]
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=20180821000010.3d93612c@windsurf \
--to=thomas.petazzoni@bootlin.com \
--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