From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/5] nodejs: use the standard configure/make options
Date: Mon, 14 Apr 2014 23:12:44 +0200 [thread overview]
Message-ID: <20140414231244.763b0d3d@skate> (raw)
In-Reply-To: <1397509552-5278-2-git-send-email-s.martin49@gmail.com>
Dear Samuel Martin,
On Mon, 14 Apr 2014 23:05:48 +0200, Samuel Martin wrote:
> Also cleanup leading whitespace.
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
> package/nodejs/nodejs.mk | 20 +++++++++++++++++---
> 1 file changed, 17 insertions(+), 3 deletions(-)
>
> diff --git a/package/nodejs/nodejs.mk b/package/nodejs/nodejs.mk
> index a44bfbd..0d84765 100644
> --- a/package/nodejs/nodejs.mk
> +++ b/package/nodejs/nodejs.mk
> @@ -23,7 +23,10 @@ define HOST_NODEJS_CONFIGURE_CMDS
> # NPM is non-functional without it, and host-openssl isn't part of
> # buildroot.
> (cd $(@D); \
> - ./configure \
> + $(HOST_CONFIGURE_OPTS) \
> + CFLAGS="$(HOST_CFLAGS)" \
> + LDFLAGS="$(HOST_LDFLAGS)" \
HOST_CONFIGURE_OPTS already contain CFLAGS and LDFLAGS definitions that
are identical to the explicit ones you're passing. So why are you
passing explicit CFLAGS and LDFLAGS ?
> + ./configure \
> --prefix=$(HOST_DIR)/usr \
> --without-snapshot \
> --without-dtrace \
> @@ -60,6 +63,8 @@ endif
> define NODEJS_CONFIGURE_CMDS
> (cd $(@D); \
> $(TARGET_CONFIGURE_OPTS) \
> + CFLAGS="$(TARGET_CFLAGS)" \
> + LDFLAGS="$(TARGET_LDFLAGS)" \
Same question here.
> LD="$(TARGET_CXX)" \
> ./configure \
> --prefix=/usr \
> @@ -75,7 +80,11 @@ define NODEJS_CONFIGURE_CMDS
> endef
>
> define NODEJS_BUILD_CMDS
> - $(TARGET_MAKE_ENV) $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D)
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) \
> + $(TARGET_CONFIGURE_OPTS) \
> + CFLAGS="$(TARGET_CFLAGS)" \
> + LDFLAGS="$(TARGET_LDFLAGS)" \
> + LD="$(TARGET_CXX)"
Same question here.
> endef
>
> #
> @@ -107,7 +116,12 @@ endef
> endif
>
> define NODEJS_INSTALL_TARGET_CMDS
> - $(MAKE) $(TARGET_CONFIGURE_OPTS) -C $(@D) DESTDIR=$(TARGET_DIR) install
> + $(TARGET_MAKE_ENV) $(MAKE) -C $(@D) install \
> + DESTDIR=$(TARGET_DIR) \
> + $(TARGET_CONFIGURE_OPTS) \
> + CFLAGS="$(TARGET_CFLAGS)" \
> + LDFLAGS="$(TARGET_LDFLAGS)" \
> + LD="$(TARGET_CXX)"
And here.
> $(NODEJS_INSTALL_MODULES)
> endef
>
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-04-14 21:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 21:05 [Buildroot] [PATCH 0/5] Python fixes Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 1/5] nodejs: use the standard configure/make options Samuel Martin
2014-04-14 21:12 ` Thomas Petazzoni [this message]
2014-04-14 21:20 ` Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 2/5] nodejs: force python interpreter Samuel Martin
2014-04-14 21:05 ` [Buildroot] [PATCH 3/5] omniorb: force python interperter Samuel Martin
2014-04-14 21:14 ` Thomas Petazzoni
2014-04-14 21:05 ` [Buildroot] [PATCH 4/5] host-python-pyrex: use the HOST_*_NEEDS_HOST_PYTHON infrastructure Samuel Martin
2014-04-14 21:15 ` Thomas Petazzoni
2014-04-14 21:22 ` Samuel Martin
2014-04-14 21:28 ` Thomas Petazzoni
2014-04-14 21:05 ` [Buildroot] [PATCH 5/5] openpgm: make its build system python2/python3 friendly Samuel Martin
2014-04-14 21:15 ` Thomas Petazzoni
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=20140414231244.763b0d3d@skate \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox