From: Christoph Egger <Christoph.Egger@amd.com>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
"xen-devel@lists.xen.org" <xen-devel@lists.xen.org>
Subject: Re: [PATCH] fix build error with seabios
Date: Wed, 25 Apr 2012 11:13:37 +0200 [thread overview]
Message-ID: <4F97C041.50205@amd.com> (raw)
In-Reply-To: <4F97BF95.6050209@amd.com>
On 04/25/12 11:10, Christoph Egger wrote:
> On 04/25/12 10:52, Ian Campbell wrote:
>
>> On Wed, 2012-04-25 at 09:43 +0100, Christoph Egger wrote:
>>> On 04/25/12 10:07, Ian Campbell wrote:
>>>
>>>> On Tue, 2012-04-24 at 18:18 +0100, Ian Jackson wrote:
>>>>> Christoph Egger writes ("[Xen-devel] [PATCH] fix build error with seabios"):
>>>>>>
>>>>>> Pass PYTHON down to seabios, so seabios will
>>>>>> use same python binary as whole xen tree does.
>>>>>> Fixes build error on NetBSD.
>>>>>
>>>>> Ian, does this look sensible to you ?
>>>>
>>>> It exports $(PYTHON) to all subdirs of tools/firmware, but I guess that
>>>> is OK, so we might as well take this now.
>>>
>>>
>>> Thanks.
>
>>>
>
>>>> Does
>>>> subdirs-seabios: PYTHON=$(PYTHON)
>>>> (or something similar) work? Might be a better option in the future
>>>
>>> No, this doesn't work.
>>
>> What about
>> subdir-all-seabios: PYTHON=...
>> ?
>
>
> No, doesn't work. I also tried without success:
>
> subdirs-all-seabios
> subdir-all-seabios-dir
> subdirs-all-seabios-dir
> seabios-dir
I found something that works:
subdir-all-seabios-dir:
export PYTHON=$(PYTHON)
Christoph
>
>>>>>
>>>>>> Signed-off-by: Christoph Egger <Christoph.Egger@amd.com>
>>>>
>>>> Acked-by: Ian Campbell <ian.campbell@citrix.com>
>>>>
>>>>>>
>>>>>> ----------------------------------------------------------------------
>>>>>> diff -r ab552da976a3 tools/firmware/Makefile
>>>>>> --- a/tools/firmware/Makefile Wed Apr 11 18:28:33 2012 +0200
>>>>>> +++ b/tools/firmware/Makefile Fri Apr 13 16:22:23 2012 +0200
>>>>>> @@ -32,7 +32,7 @@ ifeq ($(CONFIG_ROMBIOS),y)
>>>>>> false ; \
>>>>>> fi
>>>>>> endif
>>>>>> - $(MAKE) subdirs-$@
>>>>>> + $(MAKE) PYTHON=$(PYTHON) subdirs-$@
>>>>>>
>>>>>>
>>>>>> .PHONY: install
>>>>>>
>>>>>> ----------------------------------------------------------------------
>
>
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Einsteinring 24, 85689 Dornach b. Muenchen
Geschaeftsfuehrer: Alberto Bozzo, Andrew Bowd
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2012-04-25 9:13 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-13 14:23 [PATCH] fix build error with seabios Christoph Egger
2012-04-24 17:18 ` Ian Jackson
2012-04-25 8:07 ` Ian Campbell
2012-04-25 8:43 ` Christoph Egger
2012-04-25 8:52 ` Ian Campbell
2012-04-25 9:10 ` Christoph Egger
2012-04-25 9:13 ` Christoph Egger [this message]
2012-04-25 9:18 ` Christoph Egger
2012-04-25 9:20 ` Ian Campbell
2012-04-25 9:52 ` Christoph Egger
2012-04-25 9:16 ` Ian Campbell
2012-04-25 9:21 ` Christoph Egger
2012-04-25 10:23 ` Ian Jackson
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=4F97C041.50205@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=xen-devel@lists.xen.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).