From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6] support/scripts: add script to test a package
Date: Sat, 11 Feb 2017 17:08:25 +0100 [thread overview]
Message-ID: <20170211160824.GA20146@free.fr> (raw)
In-Reply-To: <70e8.589b94e3.db816@xdna.net>
Cam, All,
Since you did not Cc me on that mail, I only noticed it now...
On 2017-02-08 22:00 -0000, Cam Hutchison spake thusly:
> "Yann E. MORIN" <yann.morin.1998@free.fr> writes:
> >This script helps in testing that a package builds fine on a wide range
> >of architectures and toolchains: BE/LE, 32/64-bit, musl/glibc/uclibc...
[--SNIP--]
> >+ if [ ${#toolchains[@]} -eq 0 ]; then
> >+ printf "error: no toolchain found (networking issue?)\n" >&2; exit 1
>
> The format string should be in single quotes as it contains a glob char.
Nope, wildcards are not expanded in double quotes (as you then noticed).
> I usually put all printf format strings in single quotes since printf is
> doing the substitutions, not the shell.
I tend to agree on the principle: format strings should be
single-quoted. But then we have disparate quoting styles, and I don;t
like it. I prefer a single quoting style...
But your point is valid as well.
[--SNIP--]
> >+ while read line; do
> >+ if ! grep "^${line}\$" "${dir}/.config" >/dev/null 2>&1; then
>
> You should use grep -Fx here since ${line} might contains regex chars:
>
> if ! grep -Fx "${line}" "${dir}/.config" >/dev/null 2>&1; then
>
> ....
>
> >+ printf ", SKIPPED\n"
> >+ return
> >+ fi
> >+ done <"${cfg}"
>
> .... but I'd get rid of the loop altogether and use comm(1); something like:
>
> if [ -n "$( comm -23 <(sort "${cfg}") <(sort "${dir/.config}") )" ]; then
> printf ", SKIPPED\n"
> return
> fi
Yup, I'll take a look at using comm instead. Thanks for the tip! :-)
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2017-02-11 16:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-08 20:15 [Buildroot] [PATCH 0/6 v3] support: script to build-test packages Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 1/6] support/scripts: add script to test a package Yann E. MORIN
2017-02-08 22:00 ` Cam Hutchison
2017-02-08 22:39 ` Cam Hutchison
2017-02-11 16:08 ` Yann E. MORIN [this message]
2017-02-11 21:19 ` Thomas De Schampheleire
2017-02-11 22:28 ` Yann E. MORIN
2017-02-09 13:41 ` Luca Ceresoli
2017-02-09 21:50 ` Thomas Petazzoni
2017-02-09 22:00 ` Yann E. MORIN
2017-02-09 21:51 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 2/6] support/test-pkg: store lines missing from resulting configuraiton Yann E. MORIN
2017-02-09 17:07 ` Luca Ceresoli
2017-02-09 21:58 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 3/6] support/test-pkg: report number and types of failures Yann E. MORIN
2017-02-09 17:09 ` Luca Ceresoli
2017-02-09 21:59 ` Thomas Petazzoni
2017-02-11 19:48 ` Thomas De Schampheleire
2017-02-11 22:21 ` Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 4/6] supprt/test-pkg: add option to limit the number of tests Yann E. MORIN
2017-02-09 22:13 ` Thomas Petazzoni
2017-02-08 20:15 ` [Buildroot] [PATCH 5/6] support/test-pkg: add option to use an alternate list of toolchains Yann E. MORIN
2017-02-11 19:53 ` Thomas De Schampheleire
2017-02-11 22:24 ` Yann E. MORIN
2017-02-08 20:15 ` [Buildroot] [PATCH 6/6] support/test-pkg: print number of toolchain and progress Yann E. MORIN
2017-02-11 20:09 ` Thomas De Schampheleire
2017-02-11 22:25 ` Yann E. MORIN
2017-02-12 6:40 ` Thomas De Schampheleire
2017-02-12 9:33 ` Yann E. MORIN
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=20170211160824.GA20146@free.fr \
--to=yann.morin.1998@free.fr \
--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