make info failures on -current
There are a lot of ports failing on -current due to errors from makeinfo. I’m assuming that this is due to invalid info markup syntax. My knowledge of info is essentially zero. Past rewriting the info file itself, is there a workaround to these problems? Do these ports need makeinfo invoked in some different way, or do they require some other info processor? I’d like to start patching some of these build failures. As an example, http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p365429_s270183/logs/errors/husky-fidoconf-devel-1.9.20140519.log # Adam -- Adam Weinberger ad...@adamw.org http://www.adamw.org ___ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to freebsd-ports-unsubscr...@freebsd.org
Re: make info failures on -current
On 20 Aug 2014, at 15:59, Adam Weinberger ad...@adamw.org wrote: There are a lot of ports failing on -current due to errors from makeinfo. I’m assuming that this is due to invalid info markup syntax. My knowledge of info is essentially zero. Past rewriting the info file itself, is there a workaround to these problems? Do these ports need makeinfo invoked in some different way, or do they require some other info processor? I’d like to start patching some of these build failures. As an example, http://gohan2.ysv.freebsd.org/data/head-amd64-default-baseline/p365429_s270183/logs/errors/husky-fidoconf-devel-1.9.20140519.log Eventually I copped out, and just built world using WITH_INFO enabled... :-/ -Dimitry signature.asc Description: Message signed with OpenPGP using GPGMail
