Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/2] package/pkg-kconfig: define KCONFIG_EDITORS_MAKE_ENV
Date: Thu, 2 Jul 2015 07:44:05 +0000	[thread overview]
Message-ID: <1435823045.2966.23.camel@synopsys.com> (raw)
In-Reply-To: <1435582227-26345-2-git-send-email-talz@ezchip.com>

Hi Tal,

On Mon, 2015-06-29 at 15:50 +0300, Tal Zilcer wrote:
> From: Tal Zilcer <talz@ezchip.com>, 
> 
> When building a configuration editor we assume its for the HOST.
> However some packages might define MAKE_ENV as TARGET_MAKE_NEV.
> Using this variable adds to beginning of $(PATH),
> the directory $(HOST_DIR)/usr/bin.
> 
> This cause us to not use pkg-config from our host machine but the one
> from $(HOST_DIR)/usr/bin. This pkg-config does not support QT.
> Now when we try to run for example linux-xconfig we fail since QT is 
> not found.
> 
> To overcome this we defined a dedicated variable for the 
> configuration editors
> 
> Signed-off-by: Tal Zilcer <talz@ezchip.com>
> ---

I'm wondering why did you put 2 patches in one series?
 [1] https://patchwork.ozlabs.org/patch/489307/
 [2] https://patchwork.ozlabs.org/patch/489306/

I'd say these 2 patches solve completely different problems and so
should be posted as 2 separate patches compared to your [PATCH 1/2],
[PATCH 2/2].

The problem with series patches within series could not be applied
separately, that means chances are you may not get either applied
because:
 a) At least one patch could not be accepted by maintainer
 b) At least one patch required rework

So in case of (a) you'll need to resend appropriate patch separately
and in case of (b) you'll need to resend all patches in the series even
if only one patch was modified.

As for this one I really like it. IMHO problem and solution are very
valid.

The only note this patch won't apply clean on current master due to
recent changes in "package/pkg-kconfig.mk". I.e. rebase is required
now.

Please rebase this patch on top of the current master and resend this
patch (preferably separately from another patch of the current series).

Feel free to add:
Reviewed-by: Alexey Brodkin <abrodkin@synopsys.com>

-Alexey

  reply	other threads:[~2015-07-02  7:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-29 12:50 [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Tal Zilcer
2015-06-29 12:50 ` [Buildroot] [PATCH 2/2] package/pkg-kconfig: define KCONFIG_EDITORS_MAKE_ENV Tal Zilcer
2015-07-02  7:44   ` Alexey Brodkin [this message]
2015-07-02  7:52     ` Thomas Petazzoni
2015-07-02  7:56       ` Alexey Brodkin
2015-06-29 14:29 ` [Buildroot] [PATCH 1/2] package/gcc: fix ARC failure to build in 2 phases Thomas Petazzoni
2015-06-29 15:39   ` Tal Zilcer
2015-06-29 15:49     ` Thomas Petazzoni
2015-07-02  7:46       ` Alexey Brodkin

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=1435823045.2966.23.camel@synopsys.com \
    --to=alexey.brodkin@synopsys.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