From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@buildroot.org
Cc: Neal Frager <neal.frager@amd.com>
Subject: Re: [Buildroot] [PATCH] package/booten: Fix build on machines with modern flex / host-flex
Date: Tue, 25 Oct 2022 15:33:04 +0200 [thread overview]
Message-ID: <87a65k110v.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20221025093752.3520434-1-peter@korsgaard.com> (Peter Korsgaard's message of "Tue, 25 Oct 2022 11:37:51 +0200")
>>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
> Fixes:
> http://autobuild.buildroot.org/results/3a8/3a8b66027cde3cdd9d02745381526d52bb626a78/
> Bootgen embeds an old version of flex, but uses the system include syntax
> (#include <>) to reference it, causing conflicts on systems with the
> development headers for a modern flex version installed, leading to build
> issues like:
> ../bisonflex/bif.yy.cpp: In member function 'virtual int BIF::FlexScanner::yylex()':
> ../bisonflex/bif.yy.cpp:1608:18: error: no match for 'operator='
> (operand types are 'std::istream' {aka 'std::basic_istream<char>'} and
> 'std::istream*' {aka 'std::basic_istream<char>*'})
> Fix it by using normal local #include statements by:
> sed -i 's/<FlexLexer.h>/"FlexLexer.h"/g' *
> Patch submitted upstream: https://github.com/Xilinx/bootgen/pull/20
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-10-25 13:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 9:37 [Buildroot] [PATCH] package/booten: Fix build on machines with modern flex / host-flex Peter Korsgaard
2022-10-25 9:50 ` Frager, Neal via buildroot
2022-10-25 13:33 ` Peter Korsgaard [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=87a65k110v.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=neal.frager@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox