From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] make menuconfig problem in latest snapshot
Date: Sat, 21 Jan 2017 10:01:41 +0100 [thread overview]
Message-ID: <20170121090141.GA3623@free.fr> (raw)
In-Reply-To: <20170118175332.60e7a690@free-electrons.com>
Thomas, scsijon, All,
On 2017-01-18 17:53 +1100, Thomas Petazzoni spake thusly:
> 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?
Yes, they are OK. Besides, line 111 is not the one that was changed in
that commit. Line 111 is:
BR2_EXT_NAMES+=( "${br2_name}" )
Regards,
Yann E. MORIN.
> Thanks,
>
> Thomas
> --
> Thomas Petazzoni, CTO, Free Electrons
> Embedded Linux and Kernel engineering
> http://free-electrons.com
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
prev parent reply other threads:[~2017-01-21 9:01 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
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 [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=20170121090141.GA3623@free.fr \
--to=yann.morin.1998@free.fr \
--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