All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] environment variables with spaces (request for comments)
Date: Wed, 3 Mar 2021 17:35:38 +0100	[thread overview]
Message-ID: <d03ef3d6-6dc6-88c6-1d88-dde3ff4bd443@mind.be> (raw)
In-Reply-To: <d29457bd-026e-6c02-8da3-7385e80d7fcf@foxvalley.net>



On 02/03/2021 16:43, Dan Raymond wrote:
> I encountered a bug in Buildroot that resulted in a failure to run 'make
> linux-menuconfig'.? I tracked down the problem to a bug in
> package/pkg-kconfig.mk that was attempting to remove a set of variables from an
> environment string.? The problem is that a naive technique was being used that
> did not account for quoted variables that contained embedded spaces.? To be
> clear, 'make menuconfig' from the linux kernel tree works fine: this bug is in
> Buildroot only.? The reason I discovered this bug (and others may not) is
> because my PATH environment variable contains embedded spaces (which may be
> uncommon but valid and sometimes necessary).
> 
> I implemented/tested/submitted a patch that reliably fixes the bug.
> 
> Yann MORIN objected to my patch because he believes some of the packages
> Buildroot supports contain similar bugs.? I responded to his objection but he
> ignored my response and submitted his own patch that undermines mine by
> intentionally causing ALL make targets to fail when the PATH environment
> variable contains embedded spaces.? I don't think that starting a "patch war" is
> productive or contributes to the goals of the Buildroot community.? Can we have
> a discussion instead and come to a consensus on this matter?

 Yann's point is absolutely valid: any configuration except the most trivial one
will fail to build when PATH contains spaces, and it will do so in a
spectacularly difficult to debug way. So Yann's patch is definitely needed.

 However, that shouldn't stop us from fixing things where we can anyway.

 Thus, I'm inclined to merge both patches. However, I have some reservations
about the fix as well - I'll ventilate those in the patch thread.

 Regards,
 Arnout

      reply	other threads:[~2021-03-03 16:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-02 12:33 [Buildroot] [PATCH] support/dependencies: detect and bailout when PATH contains spaces/TABs Yann E. MORIN
2021-03-02 15:43 ` [Buildroot] environment variables with spaces (request for comments) Dan Raymond
2021-03-03 16:35   ` Arnout Vandecappelle [this message]

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=d03ef3d6-6dc6-88c6-1d88-dde3ff4bd443@mind.be \
    --to=arnout@mind.be \
    --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 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.