All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] package/nodejs: use shared c-ares if available
Date: Sun, 16 Jul 2017 09:16:20 +0200	[thread overview]
Message-ID: <20170716091620.11f40d13@windsurf> (raw)
In-Reply-To: <CAFGQKxe88yf4EMBxWdkpXBaQxyqG2XRaK=fdbA0Tae81MsU-ZA@mail.gmail.com>

Hello,

On Sun, 16 Jul 2017 00:12:33 +0100, Martin Bark wrote:

> nodejs always uses c-ares, libuv and libhttpparser, it just uses it's own
> versions by default (see https://github.com/nodejs/node/tree/master/deps).
> Not setting any options will continue to use the build in versions.

Then in this case, we want nodejs to unconditionally select c-ares,
libuv and libhttpparser. Indeed, like most distributions, we prefer to
use the external libraries rather than the built-in ones.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-07-16  7:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-15 17:38 [Buildroot] [PATCH 1/3] package/nodejs: use shared c-ares if available Martin Bark
2017-07-15 17:38 ` [Buildroot] [PATCH 2/3] package/nodejs: use shared libhttpparser " Martin Bark
2017-07-15 17:38 ` [Buildroot] [PATCH 3/3] package/nodejs: use shared libuv " Martin Bark
2017-07-15 19:44 ` [Buildroot] [PATCH 1/3] package/nodejs: use shared c-ares " Thomas Petazzoni
2017-07-15 23:12   ` Martin Bark
2017-07-16  7:16     ` Thomas Petazzoni [this message]
2017-07-17  8:43       ` Martin Bark

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=20170716091620.11f40d13@windsurf \
    --to=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.