From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/3] core: waf-package infra: add missing additional variables for each build step
Date: Sun, 4 Dec 2016 22:44:16 +0100 [thread overview]
Message-ID: <6ba5ccc4-1fdf-41fe-6fcb-0b8d0ec0978c@gmail.com> (raw)
In-Reply-To: <20161204222243.7431c24c@free-electrons.com>
Le 04/12/2016 ? 22:22, Thomas Petazzoni a ?crit :
> Hello,
>
> On Sun, 4 Dec 2016 22:20:25 +0100, Romain Naour wrote:
>
>>> Isn't it a bug of the upstream package that we need to pass --no-tests
>>> at every step?
>>
>> humm, maybe...
>> At first, I used --no-tests with AUBIO_CONF_OPTS but it's not enough.
>> All other options are saved in aubio-0.4.3/build/c4che/_cache.py
>> but not this one.
>
> It would be good to understand why.
--notests doesn't seems to be an waf option but an option used in
waflib/Tools/waf_unit_test.py. That's why it's not cached.
I'll report this issue upstream.
Best regards,
Romain
>
> Thanks,
>
> Thomas
>
next prev parent reply other threads:[~2016-12-04 21:44 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-04 20:58 [Buildroot] [PATCH 1/3] package/aubio: add upstream hash link Romain Naour
2016-12-04 20:58 ` [Buildroot] [PATCH 2/3] core: waf-package infra: add missing additional variables for each build step Romain Naour
2016-12-04 21:04 ` Thomas Petazzoni
2016-12-04 21:20 ` Romain Naour
2016-12-04 21:22 ` Thomas Petazzoni
2016-12-04 21:44 ` Romain Naour [this message]
2016-12-04 21:24 ` Yann E. MORIN
2016-12-04 21:35 ` Romain Naour
2016-12-04 21:41 ` Thomas Petazzoni
2016-12-04 23:32 ` Arnout Vandecappelle
2016-12-05 21:18 ` Romain Naour
2016-12-05 21:24 ` Thomas Petazzoni
2016-12-05 22:03 ` Arnout Vandecappelle
2016-12-04 20:58 ` [Buildroot] [PATCH 3/3] package/aubio: disable unit tests with --notests Romain Naour
2016-12-04 21:02 ` Thomas Petazzoni
2016-12-04 21:03 ` Thomas Petazzoni
2016-12-04 21:31 ` [Buildroot] [PATCH 1/3] package/aubio: add upstream hash link Thomas Petazzoni
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=6ba5ccc4-1fdf-41fe-6fcb-0b8d0ec0978c@gmail.com \
--to=romain.naour@gmail.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