Hi Paul, Le 30 juil. 2012 à 18:10, Paul Eggert a écrit :
> On 07/30/2012 08:37 AM, Akim Demaille wrote: >> Do you think this is really an issue? I figured that someone >> installing Bison is very likely to have Flex. > > That's more likely than not these days, yes, but still, > it's not a good sign that this failure occurred the first > time I tried to install Bison. Sorry about that :/ > If it's just examples, then it'd be better if Bison's > 'configure' merely issued a warning and then didn't > run the example code on the user side? The point is to install them, they're part of the documentation. > Are these > examples extracted from the manual? if so, they can > be done by the person making the tarball too. Yes, they are, but really, I've lost hours fighting issues in srcdir vs builddir, and I am not willing to spend again some time on this now. Updating in srcdir is too messy. So there would be two kinds of tarballs: those made with Flex, and those without. > The > general idea is to do as much as possible before > generating the tarball, as this makes things easier > on the installer. > > Also, suppose some day Flex requires Bison? :-) I understand this, but I see no simple means to achieve this, especially in master. If there's strong resistance agains that, I'll spend some time on this, but currently, I am really eager to finish what was started years ago and finally release C++ with variants, renamed %define variables etc.
