From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] make menuconfig problem in latest snapshot
Date: Wed, 18 Jan 2017 17:53:32 +1100 [thread overview]
Message-ID: <20170118175332.60e7a690@free-electrons.com> (raw)
In-Reply-To: <c7623806-1a06-8500-af10-e94601258f79@lamiaworks.com.au>
Hello,
On Wed, 18 Jan 2017 12:55:49 +1100, scsijon wrote:
> Found this error in todays snapshot
> --------------------------
> # make menuconfig
> support/scripts/br2-external: line 111: syntax error near unexpected
> token `"${br2_name}"'
> Makefile:197:
> /initrd/mnt/dev_save/firefox_downloads/buildroot-11/buildroot-20140118-snap/output/.br-external.mk:
> No such file or directory
> make: Failed to remake makefile
> `/initrd/mnt/dev_save/firefox_downloads/buildroot-11/buildroot-20140118-snap/output/.br-external.mk'.
> support/scripts/br2-external: line 111: syntax error near unexpected
> token `"${br2_name}"'
> make: ***
> [/initrd/mnt/dev_save/firefox_downloads/buildroot-11/buildroot-20140118-snap/output/build/.br2-external.in]
> Error 2
> #
> ----------------------------
Thanks for the report! Can you try reverting commit
05576fca13b129da8c7186ee2307981135d3391f ? I believe it's the one that
introduced the problem.
Yann, are you sure that the nested double quotes are OK?
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-01-18 6:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 1:55 [Buildroot] make menuconfig problem in latest snapshot scsijon
2017-01-18 6:53 ` Thomas Petazzoni [this message]
2017-01-18 9:40 ` scsijon
2017-01-18 10:23 ` Baruch Siach
2017-01-18 10:33 ` Peter Korsgaard
2017-01-18 23:48 ` scsijon
2017-01-20 14:03 ` Peter Korsgaard
2017-01-21 9:01 ` 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=20170118175332.60e7a690@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