On 2019 May 30 20:35:56, you wrote to me:

 ml>> mine fails when bison tries to compile the documentation... i wrote
 ml>> the maintainer and asked about it... i haven't checked my email
 ml>> today, though...

 GK> I fail to find a ticket from you on sourceforge.

i haven't posted one... the information available on SF says to contact the
current maintainer, Michael Dukelsky, which i have done... i didn't feel
like joining another mailing list and i haven't looked to see if RU.RNTRACK
is available at any of my feeds... i don't really care to join it/them for
just one or two problems... i may later on, though, once i get into
configuring it but it looks to configure very similar to netmgr... i'm not
sure what one would do with the perl scripting support but it might come in
handy at some point... for now, bouncing these few netmails is all i'm
after ;)

 GK> Is your problem with bison or flex?

bison... i don't have flex installed that i know of... i also don't know if
bison calls flex or not...

 GK> Could you post the error you get here?

the error was about " ={" and " = {" and said the
"=" was unexpected...

i took a chance and hacked all the above to just "{" (removed
those equals signs) and bison completed... there were also four or five
FILEBOX* lines that needed a ";" added before the ending
"}"... the build now completes and i've sent a diff to Michael to
use if needed/desired... said diff/patch file is 1494 lines long and i can
make it available to you/others if needed...

 GK> Do you have an easy way to try a previous version of flex/bison?

not that i know of... the system is maintained by aptitude and i'm loath to
go forcing things around... especially since it is my BBS production
machine and one of the stars for the NAB...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin'
it wrong...
... Never refuse homemade brownies.
---