From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit] Makefile: add check of binaries architecture
Date: Tue, 21 Mar 2017 17:28:36 +0100 [thread overview]
Message-ID: <20170321172836.69a3026c@free-electrons.com> (raw)
In-Reply-To: <877f3imwcd.fsf@dell.be.48ers.dk>
Hello,
On Tue, 21 Mar 2017 17:24:34 +0100, Peter Korsgaard wrote:
> Sorry for the late response (nice feature!), but doesn't this get very
> confused if any package ever install any files with spaces or special
> characters?
Yes, this would mess up if files have spaces in their names. I'll have
to think about how to handle this. Suggestions from shell gurus are
welcome, of course :)
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-21 16:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 21:22 [Buildroot] [git commit] Makefile: add check of binaries architecture Thomas Petazzoni
2017-03-21 16:24 ` Peter Korsgaard
2017-03-21 16:28 ` Thomas Petazzoni [this message]
2017-03-21 19:08 ` 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=20170321172836.69a3026c@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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