From: Peter Korsgaard <peter@korsgaard.com>
To: Bernd Kuhls <bernd.kuhls@t-online.de>, neal.frager@amd.com
Cc: buildroot@uclibc.org
Subject: Re: [Buildroot] [git commit] package/bootgen: bump to xilinx_v2023.1
Date: Mon, 12 Jun 2023 17:47:31 +0200 [thread overview]
Message-ID: <87ttvcznqk.fsf@48ers.dk> (raw)
In-Reply-To: <pan$df8d3$d38b8fa2$c50497ad$86a070c3@ID-313208.user.individual.net> (Bernd Kuhls's message of "Mon, 12 Jun 2023 16:54:32 +0200")
>>>>> "Bernd" == Bernd Kuhls <bernd.kuhls@t-online.de> writes:
> Am Tue, 16 May 2023 16:48:25 +0200 schrieb Peter Korsgaard:
>> commit:
>> https://git.buildroot.net/buildroot/commit/?
> id=e4ac14e09a57667168278187331cdf7238b80324
>> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
>>
>> This patch bumps bootgen to version xilinx_v2023.1.
>> The patch for build machines with modern flex is no longer needed.
> Hi Neal, hi Peter,
> on my machine I cannot reproduce the flex bug but it seems it occurs
> again after bumping this package which removed the patch:
> http://autobuild.buildroot.net/?reason=host-bootgen-xilinx_v2023.1
I also cannot reproduce it here, but looking at the build issues, it
seems to get confused building cmdoptions.yy.cpp which some mixup
between pointer-to vs reference-to std::iostream:
../bisonflex/cmdoptions.yy.cpp: In member function 'virtual int CO::FlexScanner::yylex()':
../bisonflex/cmdoptions.yy.cpp:1362:18: error: no match for 'operator='
(operand types are 'std::istream' {aka 'std::basic_istream<char>'} and
'std::istream*' {aka 'std::basic_istream<char>*'})
This was indeed changed in Flex 2.6 almost 8 years ago:
https://github.com/westes/flex/commit/336a1deaa57975f34cd732d656d1c0cbe3d5233a
But bootgen embeds an (ancient) flex 2.5.35:
https://github.com/Xilinx/bootgen/blob/master/bif.yy.cpp#L18-L20
It is a bit hard to follow as the 2023.1 tag seems to have a number of
squashed commits rather than the commits from master, but:
The patch was upstreamed here:
https://github.com/Xilinx/bootgen/pull/20
The patch was not applied, instead a different patch with the same
content applied to master:
https://github.com/Xilinx/bootgen/commit/af4f7083ea92931a07e47995eb2bc2a348c577ed
This patch was not applied to the xlnx_rel_v2023.1 branch, instead most
of the content was included in:
https://github.com/Xilinx/bootgen/commit/bfba91b2c84160dc203ff09f0e930d82ed06a83a
But the cmdoptions.yy.cpp hunk was (accidently?) dropped:
https://github.com/Xilinx/bootgen/commit/bfba91b2c84160dc203ff09f0e930d82ed06a83a#diff-e0287adb420dbecc112acdf7d4a1efba8ea6cbf06401e4e8679b8ffd22a091d8
I'll send a patch to fix that.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2023-06-12 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230609161307.432DD8262B__38013.4634369583$1686327210$gmane$org@busybox.osuosl.org>
2023-06-12 14:54 ` [Buildroot] [git commit] package/bootgen: bump to xilinx_v2023.1 Bernd Kuhls
2023-06-12 15:47 ` Peter Korsgaard [this message]
2023-06-12 15:58 ` Frager, Neal via buildroot
2023-05-16 14:48 Peter Korsgaard
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=87ttvcznqk.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=bernd.kuhls@t-online.de \
--cc=buildroot@uclibc.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