From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 2/2] sunxi-mali-mainline-driver: bump version and add support for building on arm64(aarch64).
Date: Fri, 24 Aug 2018 21:58:14 +0200 [thread overview]
Message-ID: <20180824215814.5366a812@windsurf> (raw)
In-Reply-To: <ac85c090-d43d-8415-5333-f8daf24e70a1@micronovasrl.com>
Hello,
On Fri, 24 Aug 2018 21:10:56 +0200, Giulio Benetti wrote:
> I'm getting problems with whitespaces in pdf filename.
> I couldn't find in Buildroot Documentation if it's allowed or not having
> filenames containing spaces.
> I've tried using:
> 'EULA for Mali 400MP _AW.pdf'
> "EULA for Mali 400MP _AW.pdf"
> etc.
> but with no luck.
>
> If it's not possible to have whitespaces, should I workaround it in
> package changing filename before legal-info recipe?
> Like:
> EULA for Mali 400MP _AW.pdf
> becoming:
> EULA_for_Mali_400MP_AW.pdf
> ?
Yes, I think it makes sense to have a POST_PATCH_HOOKS that renames the
file so that it doesn't have spaces.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-08-24 19:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-22 0:06 [Buildroot] [PATCH v2 0/2] sunxi-mali-mainline*: add arm64 build support and Giulio Benetti
2018-08-22 0:06 ` [Buildroot] [PATCH v2 1/2] sunxi-mali-mainline: add support for arm64(aarch64) architecture and r8p1 blob version Giulio Benetti
2018-08-22 11:21 ` Thomas Petazzoni
2018-08-22 0:06 ` [Buildroot] [PATCH v2 2/2] sunxi-mali-mainline-driver: bump version and add support for building on arm64(aarch64) Giulio Benetti
2018-08-22 11:29 ` Thomas Petazzoni
2018-08-22 18:37 ` Giulio Benetti
2018-08-22 19:26 ` Thomas Petazzoni
2018-08-24 19:10 ` Giulio Benetti
2018-08-24 19:58 ` Thomas Petazzoni [this message]
2018-08-24 21:14 ` Yann E. MORIN
2018-08-24 21:28 ` Giulio Benetti
2018-08-24 21:39 ` Yann E. MORIN
2018-08-26 21:36 ` Giulio Benetti
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=20180824215814.5366a812@windsurf \
--to=thomas.petazzoni@bootlin.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