All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Richard Weinberger <richard@nod.at>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Peter Foley <pefoley2@verizon.net>
Subject: Re: [GIT PULL] UML changes for 3.2
Date: Fri, 04 Nov 2011 11:41:43 +0100	[thread overview]
Message-ID: <4EB3C167.3020508@suse.cz> (raw)
In-Reply-To: <1320358228.14409.279.camel@x61.thuisdomein>

On 3.11.2011 23:10, Paul Bolle wrote:
> On Thu, 2011-11-03 at 22:56 +0100, Paul Bolle wrote:
>> These Makefiles always make me nervous. Is SUBARCH set by the time the
>> update-po-config target is run? If so, we could simply do "env SUBARCH=
>> $(SUBARCH) [...]". But how do I check that SUBARCH really is set (ie,
>> that I'm not passing env an empty string)?
> 
> It seems the trick here should be
>     env SUBARCH=$(KBUILD_BUILDHOST) [...]
> 
> Michal, does that make sense?

I doub't kxgettext needs $SUBARCH at all, it only cares about the
prompts and help texts, it does not evaluate any kconfig symbols.

Michal

  parent reply	other threads:[~2011-11-04 10:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-02 14:10 [GIT PULL] UML changes for 3.2 Richard Weinberger
2011-11-03 19:32 ` Paul Bolle
2011-11-03 20:41   ` Paul Bolle
2011-11-03 21:01     ` Paul Bolle
2011-11-03 21:15       ` Richard Weinberger
2011-11-03 21:25         ` Paul Bolle
2011-11-03 21:37           ` Richard Weinberger
2011-11-03 21:56             ` Paul Bolle
2011-11-03 22:10               ` Paul Bolle
2011-11-03 22:18                 ` Richard Weinberger
2011-11-04 10:41                 ` Michal Marek [this message]
2011-11-05 11:48                   ` Paul Bolle

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=4EB3C167.3020508@suse.cz \
    --to=mmarek@suse.cz \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=pefoley2@verizon.net \
    --cc=richard@nod.at \
    --cc=torvalds@linux-foundation.org \
    /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.