From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 4/4] package/rpm: add host variant
Date: Thu, 3 Sep 2015 22:55:05 +0200 [thread overview]
Message-ID: <20150903205505.GG3607@free.fr> (raw)
In-Reply-To: <CALe+oY8qrjgBwjXTHacFjwy=4LToG98PmrF4VjeCERSUcxVF4A@mail.gmail.com>
James, All,
On 2015-09-03 16:34 -0400, James Knight spake thusly:
> On Thu, Sep 3, 2015 at 2:35 PM, Yann E. MORIN <yann.morin.1998@free.fr> wrote:
> >
> > Same comment as for beecrypt: you do not need an intermediate variable,
> > just re-use the target variable when defining the host variable; [...]
> >
> > RPM_CONF_OPTS = \
> > --disable-largefile \
> > --disable-rpath \
> > [...]
> >
> > HOST_RPM_CONF_OPTS = \
> > $(RPM_CONF_OPTS) \
> > --with-beecrypt \
> > --without-archive \
> > [...]
>
> Question about this though, won't this be an issue for additional
> configuration values set later in the file (ie. options added to
> `RPM_CONF_OPTS`)?
>
> When I clean up this patch and remove the intermediate variable, I
> assume I should be declaring the host options such as:
>
> HOST_RPM_CONF_OPTS := \
> $(RPM_CONF_OPTS) \
> --with-beecrypt \
> --without-archive \
> [...]
>
> Unless I've missed something?
Nope, you're right. I missed the fact that additional configure flags
could be added to the target variant.
And following Arnout's comment, pleas keep the internediate variable.
However, I think it is mis-named. What about RPM_COMMON_CONF_OPTS ?
Ditto for beecrypt, of course.
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. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-09-03 20:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 15:23 [Buildroot] [PATCH v3 1/4] package/rpm: bump to version 4.12.0.1 James Knight
2015-09-03 15:23 ` [Buildroot] [PATCH v3 2/4] package/berkeleydb: add host variant James Knight
2015-09-03 16:13 ` Yann E. MORIN
2015-09-03 15:23 ` [Buildroot] [PATCH v3 3/4] package/beecrypt: " James Knight
2015-09-03 16:15 ` Yann E. MORIN
2015-09-03 16:32 ` Yann E. MORIN
2015-09-03 20:39 ` Arnout Vandecappelle
2015-09-03 15:23 ` [Buildroot] [PATCH v3 4/4] package/rpm: " James Knight
2015-09-03 18:35 ` Yann E. MORIN
2015-09-03 20:34 ` James Knight
2015-09-03 20:55 ` Yann E. MORIN [this message]
2015-09-04 11:22 ` [Buildroot] [PATCH v3 1/4] package/rpm: bump to version 4.12.0.1 Vicente Olivert Riera
2015-10-03 14:15 ` Peter Korsgaard
2015-10-05 14:31 ` James Knight
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=20150903205505.GG3607@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