From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] package/nodejs: fix build error without OpenSSL support
Date: Tue, 18 Nov 2014 22:03:30 +0100 [thread overview]
Message-ID: <874mtwp6fx.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1416224516-6065-1-git-send-email-jkrause@posteo.de> ("Jörg Krause"'s message of "Mon, 17 Nov 2014 12:41:55 +0100")
>>>>> "J?rg" == J?rg Krause <jkrause@posteo.de> writes:
> Add a patch to fix broken build of nodejs without OpenSSL support.
> Version 0.10.33 of nodejs introduced a bug which prevents us from building
> nodejs without OpenSSL support. The bug is reported upstream:
> https://github.com/joyent/node/issues/8676
> This bug caused some build errors:
> * http://autobuild.buildroot.net/results/0bf/0bf17bf710db051d491123482c90f2f72810804b/
> * http://autobuild.buildroot.net/results/e1f/e1fb34818ff1167aa008b4011befb9fd14c81293/
> and more...
> Signed-off-by: J?rg Krause <jkrause@posteo.de>
> ---
> Changes v1 -> v2:
> - patch nodejs to allow building without OpenSSL support (Thomas)
> - adapt commit log
Committed, thanks. Please don't forget to send the patch upstream.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-11-18 21:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 11:41 [Buildroot] [PATCH 1/2] package/nodejs: fix build error without OpenSSL support Jörg Krause
2014-11-17 11:41 ` [Buildroot] [PATCH 2/2] package/nodejs: remove config options --without-ssl2 and --without-ssl3 Jörg Krause
2014-11-17 17:38 ` Fabio Porcedda
2014-11-17 18:01 ` Fabio Porcedda
2014-11-18 21:06 ` Peter Korsgaard
2014-11-17 17:43 ` [Buildroot] [PATCH 1/2] package/nodejs: fix build error without OpenSSL support Fabio Porcedda
2014-11-17 18:39 ` Jörg Krause
2014-11-18 21:03 ` Peter Korsgaard [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=874mtwp6fx.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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