All of lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libxmlrpc: fix static build
Date: Fri, 19 Jun 2015 07:34:21 +0300	[thread overview]
Message-ID: <20150619043421.GU8165@tarshish> (raw)
In-Reply-To: <20150614230049.6ab5e979@free-electrons.com>

Hi Thomas,

On Sun, Jun 14, 2015 at 11:00:49PM +0200, Thomas Petazzoni wrote:
> 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.

I looked around and I found a few more packages that might benefit from 
_MAKE_VARS. But I thing the gain is not enough to worth the trouble. Adding 
$(2)_MAKE_VARS might also lead to confusion when a user sets both _MAKE_VARS 
and one or more other _OPTS, thus silently overriding _MAKE_VARS in a way that 
is not apparent to the reader.

So, I suggest to just apply the original patch.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

      parent reply	other threads:[~2015-06-19  4:34 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
2015-06-19  4:34       ` Baruch Siach [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=20150619043421.GU8165@tarshish \
    --to=baruch@tkos.co.il \
    --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.