thr3ads.net - llvm dev - [LLVMdev] [Cygwin] groff build error [May 2005]

If this information is useful, please help other people find it:
Share via:

Aaron Gray

2005-May-19 22:12 UTC

[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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20050519/20443d96/attachment.html>

Reid Spencer

2005-May-19 22:27 UTC

head link

[LLVMdev] [Cygwin] groff build error

Aaron,

This looks to be exactly the same problem as with the executables.
There's probably a space where it shouldn't be. Either that or the
CommandGuide directory isn't getting created properly.


Reid

On Thu, 2005-05-19 at 23:12 +0100, Aaron Gray wrote:> 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-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20050519/3edfd8df/attachment.sig>

Aaron Gray

2005-May-19 22:50 UTC

head link

[LLVMdev] [Cygwin] groff build error

>This looks to be exactly the same problem as with the executables.
>There's probably a space where it shouldn't be. Either that or the
>CommandGuide directory isn't getting created properly.
Okay, I will have a bit more confidence and look into it.

I will have to leave it to tommorow as it is getting late and I have to get 
up early.

Many thanks,

Aaron

Aaron Gray

2005-May-20 14:13 UTC

head link

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

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 ?

Aaron

  ----- Original Message ----- 
  From: Aaron Gray 
  To: LLVM Developers Mailing List 
  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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20050520/a2934d9e/attachment.html>

John Criswell

2005-May-20 14:23 UTC

head link

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

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.

Reid Spencer

2005-May-20 14:27 UTC

head link

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

Yeah, that's exactly right, Aaron. "true" is a command that simply
returns with an exit status of 0 and ignores its arguments. When pod2man
can't be found we define the variable that specifies its path as "true
pod2man". This allows the command that should have been run to be shown
while at the same time not interrupting the makefile with a failure.
This is entirely intentional.

Once you've installed Perl, you need to reconfigure your build tree to
get the appropriate variable defined properly. Check your
Makefile.config file (generated by configure) to determine if the PERL
variable has been set properly. Also look for anything else that starts
with "true" as you'll need those programs too.

Reid.

On Fri, 2005-05-20 at 15:13 +0100, 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 ?
>  
> Aaron
>  
>         ----- Original Message ----- 
>         From: Aaron Gray 
>         To: LLVM Developers Mailing List 
>         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-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20050520/c079aef0/attachment.sig>

Aaron Gray

2005-May-20 14:43 UTC

head link

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

Okay, run a 'configure' and build again !
  ----- Original Message ----- 
  From: Aaron Gray 
  To: LLVM Developers Mailing List 
  Sent: Friday, May 20, 2005 3:13 PM
  Subject: Re: [LLVMdev] [Cygwin] groff build error - semi solved


  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 ?

  Aaron

    ----- Original Message ----- 
    From: Aaron Gray 
    To: LLVM Developers Mailing List 
    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
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.llvm.org/pipermail/llvm-dev/attachments/20050520/7fc359d6/attachment.html>

Maybe Matching Threads

Search for more maybe matching threads

llvm dev - May 2005 - [LLVMdev] [Cygwin] groff build error

[LLVMdev] [Cygwin] groff build error

[LLVMdev] [Cygwin] groff build error

[LLVMdev] [Cygwin] groff build error

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

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

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

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

Maybe Matching Threads