Re: dovecot, configure and documentation as hardstop
On 19/11/2016 15:09, Aki Tuomi wrote: Michael At the moment, pandoc is only*required* if you are building from git. And it's not even required then, just do env PANDOC=true ./configure ... Aki Thanks! guess I should have read ./configure --help more closely. So, is there something else I have forgotten - in order to get a good summary of the results of 'make check'? Michael
Re: dovecot, configure and documentation as hardstop
> On November 19, 2016 at 4:01 PM Michael Felt wrote: > > > Hi, > > As preparations for a port to AIX - making sure I can get it to build on > linux with gcc. While it is fairly easy to add the requirements (on GNU > Linux) having pandoc as a configure "hardstop", even with --without-docs > or --with-docs=no is a bit worrisome as I am fearful that I amy not be > able to get pandoc ported as well. > > Hence a request that a missing pandoc become a warnig, and just not done > when pandoc is not available, or at least accept one of --without-docs > and --with-docs=no (or should I be using --with-pandata=no? ) > > Michael At the moment, pandoc is only *required* if you are building from git. And it's not even required then, just do env PANDOC=true ./configure ... Aki
dovecot, configure and documentation as hardstop
Hi, As preparations for a port to AIX - making sure I can get it to build on linux with gcc. While it is fairly easy to add the requirements (on GNU Linux) having pandoc as a configure "hardstop", even with --without-docs or --with-docs=no is a bit worrisome as I am fearful that I amy not be able to get pandoc ported as well. Hence a request that a missing pandoc become a warnig, and just not done when pandoc is not available, or at least accept one of --without-docs and --with-docs=no (or should I be using --with-pandata=no? ) Michael
