From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 9886] New: Build fails with "unexpected EOF while looking for matching `"'" if PATH contains a newline
Date: Sat, 20 May 2017 07:38:07 +0000 [thread overview]
Message-ID: <bug-9886-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=9886
Bug ID: 9886
Summary: Build fails with "unexpected EOF while looking for
matching `"'" if PATH contains a newline
Product: buildroot
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
Assignee: unassigned at buildroot.uclibc.org
Reporter: ciro.santilli at gmail.com
CC: buildroot at uclibc.org
Target Milestone: ---
I know newlines in PATH are bad, but we shouldn't punish unsuspecting users
with unhelpful error messages because of it :-)
Reproduce:
git checkout 4d1c2c82e8945a5847d636458f3825c55529835b
make qemu_x86_64_defconfig
PATH="$PATH:"$'\n'":lalala" make
Gives:
>>> host-lzip 1.18 Downloading
/bin/bash: -c: line 0: unexpected EOF while looking for matching `"'
/bin/bash: -c: line 1: syntax error: unexpected end of file
package/pkg-generic.mk:139: recipe for target
'/data/git/buildroot/output/build/host-lzip-1.18/.stamp_downloaded' failed
make[1]: ***
[/data/git/buildroot/output/build/host-lzip-1.18/.stamp_downloaded] Error 1
Makefile:79: recipe for target '_all' failed
make: *** [_all] Error 2
--
You are receiving this mail because:
You are on the CC list for the bug.
next reply other threads:[~2017-05-20 7:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-20 7:38 bugzilla at busybox.net [this message]
2017-05-20 8:22 ` [Buildroot] [Bug 9886] Build fails with "unexpected EOF while looking for matching `"'" if PATH contains a newline bugzilla at busybox.net
2017-05-20 9:37 ` bugzilla at busybox.net
2017-06-08 19:43 ` bugzilla at busybox.net
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=bug-9886-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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.