similar to: [LLVMdev] [Cygwin] llvm 'make install' build errors

Displaying 20 results from an estimated 4000 matches similar to: "[LLVMdev] [Cygwin] llvm 'make install' build errors"

2005 May 19
0
[LLVMdev] [Cygwin] llvm 'make install' build errors
Aaron, That looks to me like the "install" program on your platform isn't quite up to snuff. It should be doing a command like: /usr/bin/install -c -m 0755 \ /proj/llvm/build/Debug/bin/llvm-ranlib /proj/install/bin/llvm-ranlib Its not supposed to create an llvm-ranlib directory, the second argument is the name of the file to create. This works fine on linux. Can you "make
2005 May 14
4
[LLVMdev] Cygwin LLVM Install Errors
AFAICT these are valid errors. Getting an error on the 'make install' for LLVM :- make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar /usr/bin/install: target `/usr/llvm/bin/llvm-ar' is not a directory make[2]: *** [/usr/llvm/bin/llvm-ar] Error 1 make[2]: Leaving directory `/usr/build/llvm/tools/llvm-ar' make[1]: ***
2005 May 19
6
[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
2005 May 14
0
[LLVMdev] Cygwin LLVM Install Errors
I can't reproduce these on GNU-Linux/x86. What platform are you on? Reid. On Sat, 2005-05-14 at 16:50 +0100, Aaron Gray wrote: > AFAICT these are valid errors. > > Getting an error on the 'make install' for LLVM :- > > > make[2]: Entering directory `/usr/build/llvm/tools/llvm-ar' > llvm[2]: Installing Debug /usr/llvm/bin/llvm-ar > /usr/bin/install:
2005 May 20
2
[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
2005 May 20
0
[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 >
2012 Nov 06
0
[LLVMdev] Binutils and LLVM - gathering information
On Tue, Nov 6, 2012 at 2:19 PM, Marshall Clow <mclow.lists at gmail.com> wrote: > Binutils and LLVM > > As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. > > As a start, I'd like to summarize the current status, and
2005 May 19
0
[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
2012 Nov 06
10
[LLVMdev] Binutils and LLVM - gathering information
Binutils and LLVM As part of "owning our own toolchain", various people have expressed an interest and have been working on creating various tools that duplicate the functionality of tools available on other systems. As a start, I'd like to summarize the current status, and ask people for help updating the list. List taken from <http://www.gnu.org/software/binutils/>
2004 Oct 23
1
[LLVMdev] UPDATE: Makefile.rules Changes (IMPORTANT)
If you're on the new Makefile system, you will want to update your Makefile.rules. The patch below provides some important fixes for parallel builds and dependencies. It also adds some new features like the -local targets. For example, you can now build "all-local" to build the local directory without recursing into subdirectories. See the comments below for details of the change.
2001 Jan 11
3
contrib/redhat/openssh.spec question
I have a couple of questions regarding openssh.spec and the rpm that gets generated from it. I am using 2.3.0p1 1. Why is openssl a prereq? openssh statically links to openssl during build by default (rightfully so, you don't want your security library a shared object if possible) 2. I don't understand the following line in the spec file during the install step (it makes it not build for
2007 Mar 26
1
[LLVMdev] llvm installation failure
I am trying to make and install a version of llvm that I check out of cvs last night. When I configured LLVM, I set the prefix to a directory inside my home directory. However, when I did a make install I got the following errors: llvm[3]: Installing Debug Bytecode Archive /lib/libc.a /usr/bin/install: cannot create regular file `/lib/libc.a': Permission denied make[3]: ***
2005 May 19
2
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid, Looks like the "make TOOL_VERBOSE=1 -C tools install" was fine. I have got :- install (GNU coreutils) 5.3.0 The copyright is 2005 so I would have thought it would be allright ??? Thanks, Aaron
2005 May 19
3
[LLVMdev] [Cygwin] llvm 'make install' build errors
Reid, I think it is the first time it is run that the errors occcur !? Not sure but that would seem logical. Aaron
2005 Feb 17
2
[LLVMdev] LLVM CFE bootstrap problem at FreeBSD after last $(Install) changes in Makefile.rules
Command from LLVM CFE bootstrap sequence at FreeBSD: gmake -C runtime install-bytecode terminated with error (verbose mode): --8X------------------------------------------------------- llvm[2]: Installing Debug Bytecode Archive /usr/home/wanderer/pkg/build/llvm/night/cfe/bin/../lib/libcrtend.a /usr/bin/install -c -D /usr/home/wanderer/pkg/build/llvm/obj/Debug/lib/libcrtend.bca
2007 Oct 02
4
[LLVMdev] OCaml Install Error
Hi, I get this error duing a "make install": llvm[3]: Installing Debug /usr/local/lib/ocaml/libllvm.a install: /usr/local/lib/ocaml/libllvm.a: Permission denied make[3]: *** [install-a] Error 71 make[2]: *** [install] Error 1 make[1]: *** [ocaml/.makeinstall] Error 2 make: *** [install] Error 1 -bw
2016 Aug 09
2
[LTO] Bypass the integrated assembler ...
> On Aug 9, 2016, at 9:24 AM, Kevin Choi via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > -Wl,--plugin=LLVMgold.so,--plugin-opt=emit-llvm This is totally Gold specific. The fact that he mentions using LTOCodeGenerator makes me think that he does not use Gold. > > http://llvm.org/docs/CommandGuide/opt.html <http://llvm.org/docs/CommandGuide/opt.html> >
2017 Aug 10
2
Is anyone experienced writing Sphinx documentation?
I've read through the docs, but honestly this is driving me crazy and I shouldn't have to fight this hard to just to write some documentation. Here's the problem: Look at llvm/docs/CommandGuide/FileCheck.rst I want to add a table of contents that looks like this [ http://llvm.org/docs/CMake.html] to that file. Nothing I've tried works. (Also, no I'm not trying to add it in
2012 Jan 28
1
[LLVMdev] CommandGuide documentation points to outdated pages?
Hello, I noticed something strange in the links from http://llvm.org/docs/CommandGuide/index.html They all point to HTML files in http://llvm.org/cmds/, which were last updated on 11-May-2010. There were many updates to the CommandGuide documents since that time, according to the SVN logs, however. One manifestation of this problem is that a fix made in r147721 (07-Jan-2012) to one of the
2005 May 20
0
[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