From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Lang Daniel <d.lang@abatec.at>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH 1/1] toolchain: handle white spaces in sysroot path
Date: Wed, 27 Jul 2022 09:13:31 +0200 [thread overview]
Message-ID: <20220727091331.00d0280f@windsurf> (raw)
In-Reply-To: <VI1P190MB04938F3268FC60B09BB31E5C9F979@VI1P190MB0493.EURP190.PROD.OUTLOOK.COM>
Hello Daniel,
On Wed, 27 Jul 2022 06:36:14 +0000
Lang Daniel <d.lang@abatec.at> wrote:
> I came across this problem while using paho-mqtt-c with a staging path
> that doesn't contain spaces, but the package creates
> "$(STAGING_DIR)/usr/share/doc/Eclipse Paho C/" - which contains
> spaces. When changing/updating the external toolchain that we use,
> the subsequent build failed:
Aaah! Thanks for the extra information, makes sense. I think it would
be good to fix this maho-mqtt-c package to not use paths with spaces,
though.
Thanks again!
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-07-27 7:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 10:32 [Buildroot] [PATCH 1/1] toolchain: handle white spaces in sysroot path Lang Daniel via buildroot
2022-07-26 21:31 ` Thomas Petazzoni via buildroot
2022-07-27 6:36 ` Lang Daniel via buildroot
2022-07-27 7:13 ` Thomas Petazzoni via buildroot [this message]
2022-07-27 8:47 ` Arnout Vandecappelle
2022-08-29 6:22 ` Peter Korsgaard
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=20220727091331.00d0280f@windsurf \
--to=buildroot@buildroot.org \
--cc=d.lang@abatec.at \
--cc=thomas.petazzoni@bootlin.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.