On Thu, Apr 29, 2021 at 09:44:31AM +0200, Marc Espie wrote: > On Thu, Apr 29, 2021 at 08:30:40AM +0100, Stuart Henderson wrote: > > I don't say it often as it usually makes sense to do a targetted build > > instead, but this could do with a test in bulk. I'll run one on i386, it > > will take a few days. > > > > I've tried updating bison past 3.4 before but bailed for some reason, it > > might have been a problem with some port using it, or it might just have > > been that 3.4 makes it harder to remove the GNU m4 dependency (there was > > once an idea to try and get this working with base m4 again). > > > It's still an idea... there were two distinct problems last time I looked > - gnum4 is very lazy when it comes to closing statements. If I recall > right, you had some macro stuff that did span some include statement... > > - there are a few more emacs regexps that we don't properly mogrify, > and bison m4 happens to use them.... > > it shouldn't be impossible to fix, just requires a good sitdown and figuring > these out. > > There might be a 3rd issue still...
And there's also the fact that with the "quick start" dpb go since a few years back, it's now much harder to get it stalled on full bulks, since it starts building important ports right away, and both gnu m4 and bison usually get pulled in that dependency chain.
