From: Sergey Fedorov <serge.fdrv@gmail.com>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: peter.maydell@linaro.org, qemu-devel@nongnu.org,
david@gibson.dropbear.id.au
Subject: Re: [Qemu-devel] [PATCH v2 4/5] ./configure: accept stems to match a range of targets
Date: Thu, 24 Mar 2016 19:07:47 +0300 [thread overview]
Message-ID: <56F410D3.6030105@gmail.com> (raw)
In-Reply-To: <87bn63rhdk.fsf@linaro.org>
On 24/03/16 19:05, Alex Bennée wrote:
> Sergey Fedorov <serge.fdrv@gmail.com> writes:
>
>> On 24/03/16 15:05, Alex Bennée wrote:
>>> Sergey Fedorov <serge.fdrv@gmail.com> writes:
>>>
>>>> On 23/03/16 20:20, Alex Bennée wrote:
>>>>> diff --git a/configure b/configure
>>>>> index b88d0db..ebf8a42 100755
>>>>> --- a/configure
>>>>> +++ b/configure
>>>>> @@ -1246,7 +1246,8 @@ Standard options:
>>>>> --target-list=LIST set target list (default: build everything)
>>>>> $(echo Available targets: $default_target_list | \
>>>>> fold -s -w 53 | sed -e 's/^/ /')
>>>>> -
>>>>> + LIST can contain stems to match sets of targets
>>>>> + (e.g. softmmu will match all softmmu targets)
>>>>> Advanced options (experts only):
>>>>> --source-path=PATH path of source code [$source_path]
>>>>> --cross-prefix=PREFIX use PREFIX for compile tools [$cross_prefix]
>>>> Maybe we'd better require user to specify the exact glob patterns in
>>>> '--target-list' to avoid possible misuse?
>>> Don't you run into problems of escaping glob patterns from the shell and
>>> the like? For example if I do:
>>>
>>> 12:04 alex@zen/x86_64 [qemu.git/mttcg/base-patches-v2] >./configure
>>> --target-list=arm*
>>>
>>> ERROR: Unknown target name 'arm-softmmu-config-devices.mak.d'
>>>
>>> As the shell picks up file names from the src dir.
>>>
>> Of course, it would be necessary to quote it like this:
>>
>> ./configure --target-list='arm*'
> Hmm shell quoting is a black art it seems:
>
> 16:04 alex@zen/x86_64 [qemu.git/travis/add-trusty-gce] >./configure --target-list='ar*'
>
> ERROR: Unknown target name 'arch_init.c'
Right, it's inherent problem, I think :)
next prev parent reply other threads:[~2016-03-24 16:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 17:20 [Qemu-devel] [PATCH v2 0/5] travis: reduce the matrix, add OSX, speed-up builds Alex Bennée
2016-03-23 17:20 ` [Qemu-devel] [PATCH v2 1/5] .travis.yml: collapse the test matrix Alex Bennée
2016-03-23 17:20 ` [Qemu-devel] [PATCH v2 2/5] .travis.yml: enable OSX builds Alex Bennée
2016-03-31 13:42 ` Alex Bennée
2016-04-04 14:47 ` Peter Maydell
2016-03-23 17:20 ` [Qemu-devel] [PATCH v2 3/5] .travis.yml: make -j3 Alex Bennée
2016-03-23 17:20 ` [Qemu-devel] [PATCH v2 4/5] ./configure: accept stems to match a range of targets Alex Bennée
2016-03-24 9:23 ` Sergey Fedorov
2016-03-24 12:05 ` Alex Bennée
2016-03-24 12:16 ` Sergey Fedorov
2016-03-24 16:05 ` Alex Bennée
2016-03-24 16:07 ` Sergey Fedorov [this message]
2016-03-24 16:20 ` Alex Bennée
2016-03-24 16:46 ` Sergey Fedorov
2016-03-23 17:20 ` [Qemu-devel] [PATCH v2 5/5] .travis.yml: reduce target list on core configure tweaks Alex Bennée
2016-03-24 0:22 ` David Gibson
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=56F410D3.6030105@gmail.com \
--to=serge.fdrv@gmail.com \
--cc=alex.bennee@linaro.org \
--cc=david@gibson.dropbear.id.au \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.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).