Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libxmlrpc: fix static build
Date: Sun, 14 Jun 2015 23:48:13 +0200	[thread overview]
Message-ID: <557DF69D.2060903@mind.be> (raw)
In-Reply-To: <20150614230049.6ab5e979@free-electrons.com>

On 06/14/15 23:00, Thomas Petazzoni wrote:
> Dear Baruch Siach,
> 
> On Sun, 14 Jun 2015 22:07:38 +0300, Baruch Siach wrote:
> 
>> Unfortunately, these make variables are set explicitly in common.mk. So 
>> passing them in make environment has no effect.
> 
> Argh, ok.
> 
>> Now that I think about it, why don't we have a similar thing for MAKE_OPTS, 
>> say, $(PKG)_MAKE_VARS. Something like (untested, host packages missing):
>>
>> diff --git a/package/pkg-autotools.mk b/package/pkg-autotools.mk
>> index 1d694f0618fc..27ff16235f27 100644
>> --- a/package/pkg-autotools.mk
>> +++ b/package/pkg-autotools.mk
>> @@ -154,10 +154,10 @@ endif
>>  $(2)_CONF_ENV			?=
>>  $(2)_CONF_OPTS			?=
>>  $(2)_MAKE_ENV			?=
>> -$(2)_MAKE_OPTS			?=
>> -$(2)_INSTALL_OPTS                ?= install
>> -$(2)_INSTALL_STAGING_OPTS	?= DESTDIR=$$(STAGING_DIR) install
>> -$(2)_INSTALL_TARGET_OPTS		?= DESTDIR=$$(TARGET_DIR)  install
>> +$(2)_MAKE_OPTS			?= $$($(2)_MAKE_VARS)
>> +$(2)_INSTALL_OPTS		?= $$($(2)_MAKE_VARS) install
>> +$(2)_INSTALL_STAGING_OPTS	?= $$($(2)_MAKE_VARS) DESTDIR=$$(STAGING_DIR) install
>> +$(2)_INSTALL_TARGET_OPTS	?= $$($(2)_MAKE_VARS) DESTDIR=$$(TARGET_DIR) install
> 
> Why not. Though I'd be more convinced if there is some evidence that it
> would also be useful for other packages.
> 
> Or maybe we simply need to make $(2)_MAKE_OPTS used for both the build
> and install steps?

 Well, MAKE_OPTS includes the target that has to be built, so it can't just be
reused as is for _INSTALL. So Baruch's proposal makes more sense to me.

 Regards,
 Arnout

> 
> Best regards,
> 
> Thomas
> 


-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  reply	other threads:[~2015-06-14 21:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-09 14:20 [Buildroot] [PATCH] libxmlrpc: fix static build Baruch Siach
2015-06-12 21:13 ` Thomas Petazzoni
2015-06-14 19:07   ` Baruch Siach
2015-06-14 21:00     ` Thomas Petazzoni
2015-06-14 21:48       ` Arnout Vandecappelle [this message]
2015-06-19  4:34       ` Baruch Siach

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=557DF69D.2060903@mind.be \
    --to=arnout@mind.be \
    --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