From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/nodejs: disable for static build
Date: Mon, 3 Aug 2015 18:26:37 +0200 [thread overview]
Message-ID: <20150803162637.GM3647@free.fr> (raw)
In-Reply-To: <20150803111403.53eb7ffb@free-electrons.com>
Thomas, All,
On 2015-08-03 11:14 +0200, Thomas Petazzoni spake thusly:
> Yann,
>
> On Sun, 2 Aug 2015 17:23:33 +0200, Yann E. MORIN wrote:
>
> > > diff --git a/package/nodejs/Config.in b/package/nodejs/Config.in
> > > index c5ec792..69063fc 100644
> > > --- a/package/nodejs/Config.in
> > > +++ b/package/nodejs/Config.in
> > > @@ -8,17 +8,18 @@ config BR2_PACKAGE_NODEJS
> > > depends on !BR2_ARM_CPU_ARMV4
> > > # uses fork()
> > > depends on BR2_USE_MMU
> > > + depends on !BR2_STATIC_LIBS # dlopen, etc.
> >
> > That's not entirely true. For armv5, nodejs 0.10 does not require
> > dynamic libraries.
>
> Do we really care? Nodejs is a big stuff, unlikely to be used in
> static-only configurations. Plus the latest version of NodeJS, 0.12.x,
> no longer supports ARMv5. So I'm tempted to simply not support static
> linking at all, even if indeed for a very specific case it could be
> supported.
>
> What do you think?
Even though this is not "optimum", that's OK for me.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2015-08-03 16:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-02 9:07 [Buildroot] [PATCH 1/1] package/nodejs: disable for static build Jörg Krause
2015-08-02 15:23 ` Yann E. MORIN
2015-08-03 9:14 ` Thomas Petazzoni
2015-08-03 16:26 ` Yann E. MORIN [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=20150803162637.GM3647@free.fr \
--to=yann.morin.1998@free.fr \
--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