[LLVMdev] [Cygwin] groff build error - semi solved

[John Criswell]

Aaron Gray wrote:
> Turns out I did not have Perl installed and hence no pod2man command, so 
> it was not groff after all.
>  
> But 'true', what ever it does, does not seem to be working on Cygwin.
>  
> true pod2man --release=1.5 --center="LLVM Command Guide" 
> /usr/build/llvm/../../src/llvm-1.5/docs/CommandGuide/analyze.pod 
> /usr/build/llvm/docs/CommandGuide/analyze.1
>  
> 'true' seems to behaving like a "do nothing machine".
>  
>  From looking at the Bash documentation it does not look like it should 
> be there at all !
>  
>         http://www.faqs.org/docs/bashman/bashref_68.html
>  
> Can anyone enlighten me please as to what 'true' is doing there, and can 
> I remove it ?

This is just a guess, but look in Makefile.config for the POD2MAN 
variable and see if that's where true is coming from.

I think some of our autoconf magic uses the true command whenever it 
can't find a particular program.  That way, the Makefile rules just use 
a macro to run <program>, and if program doesn't exist, it just runs 
"true", which does nothing.

-- John T.

>  
> Aaron
>  
> 
>     ----- Original Message -----
>     *From:* Aaron Gray <mailto:angray at beeb.net>
>     *To:* LLVM Developers Mailing List <mailto:llvmdev at cs.uiuc.edu>
>     *Sent:* Thursday, May 19, 2005 11:12 PM
>     *Subject:* [LLVMdev] [Cygwin] groff build error
> 
>     Here it is, a missing file "analyze.1" :-
>      
>     /usr/bin/groff -Tps -man /usr/build/llvm/docs/CommandGuide/analyze.1
>      > /usr/buil
>     d/llvm/docs/CommandGuide/analyze.ps
>     troff: fatal error: can't open
>     `/usr/build/llvm/docs/CommandGuide/analyze.1': No
>      such file or directory
>     make[2]: *** [/usr/build/llvm/docs/CommandGuide/analyze.ps] Error 1
>     make[2]: Leaving directory `/usr/build/llvm/docs/CommandGuide'
>     make[1]: *** [install] Error 1
>     make[1]: Leaving directory `/usr/build/llvm/docs'
>     make: *** [install] Error 1
>      
>     Whoopse, this is actually the pre 1.5 version of llvm I am using, so
>     I do not know whether it has been fixed in the 1.5 release, probably
>     not, but if it is not obvious, please, do not waste too much time on
>     it, and I will do a clean 1.5 rebuild tomorrow, then hopefully a CVS
>     build.
>      
>     Hopefully I can put together a sh script and makefile combination to
>     automate the build process.
>      
>     Aaron
>      
> 
>     ------------------------------------------------------------------------
> 
>     _______________________________________________
>     LLVM Developers mailing list
>     LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>     http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
> http://mail.cs.uiuc.edu/mailman/listinfo/llvmdev


-- 
John T. Criswell
Research Programmer
University of Illinois at Urbana-Champaign
"It's today!" said Piglet. "My favorite day," said Pooh.