search for: ginstall

Hi, I tried to install LLVM in our server, but after successfully compiling it, the installation failed. The reported error is: llvm[1]: Installing HTML documentation /usr/dcs/software/supported/bin/ginstall: invalid option -- C Try `/usr/dcs/software/supported/bin/ginstall --help' for more information. gmake[1]: *** [install-html] Error 1 gmake[1]: Leaving directory `/home/software/llvm/docs' gmake: *** [install] Error 1 I am wondering if some specific version of the install program is...

On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote: > llvm[1]: Installing HTML documentation > /usr/dcs/software/supported/bin/ginstall: invalid option -- C > Try `/usr/dcs/software/supported/bin/ginstall --help' for more information. /usr/dcs/software/supported/bin/ginstall is version 4.0, whereas Fedora Core 1 (which is QUITE old) has /usr/bin/install version 5.0 . Even install-4.5.3 has the -C switch. For now, manually...

...hange will have to go into docs/Makefile. Either that or upgrade install to version 5. Reid. On Thu, 2005-02-17 at 11:33, Misha Brukman wrote: > On Thu, Feb 17, 2005 at 01:21:20PM -0600, Feng Chen wrote: > > llvm[1]: Installing HTML documentation > > /usr/dcs/software/supported/bin/ginstall: invalid option -- C > > Try `/usr/dcs/software/supported/bin/ginstall --help' for more information. > > /usr/dcs/software/supported/bin/ginstall is version 4.0, whereas Fedora > Core 1 (which is QUITE old) has /usr/bin/install version 5.0 . > > Even install-4.5.3 has the...

...GNU install. We're talking about the -C option (uppercase). > The -C option is used directly in docs/Makefile. So the change will have > to go into docs/Makefile. Either that or upgrade install to version 5. docs/Makefile uses $(INSTALL) -C (uppercase). My point is that /usr/dcs/..../ginstall doesn't accept -C but /usr/bin/install does. Changing it in Makefile.config will do the trick. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

On Dec 16, 2008, at 10:34 AM, Jeffrey Yasskin wrote: > I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also > checked out llvm. Both are synced to r61075. hi Jeffrey, This patch should have fixed the problem: http://lists.cs.uiuc.edu/pipermail/llvm-commits/Week-of-Mon-20081215/071210.html Please update and try again, sorry for the breakage! -Chris

...4.2/trunk/obj/../install/i686-apple-darwin9" "target_alias=i686-apple-darwin9" "BISON=bison" "CC_FOR_BUILD=gcc -m32" "CFLAGS_FOR_BUILD=-g -O2" "CXX_FOR_BUILD=g++ -m32" "EXPECT=expect" "FLEX=flex" "INSTALL=/opt/local/bin/ginstall -c" "INSTALL_DATA=/opt/local/bin/ginstall -c -m 644" "INSTALL_PROGRAM=/opt/local/bin/ginstall -c" "INSTALL_SCRIPT=/opt/local/bin/ginstall -c" "LEX=flex" "M4=gm4" "MAKE=make" "RUNTEST=runtest" "RUNTESTFLAGS=" "...

I'm on OSX 10.5, trying to build a svn checkout of llvm-gcc. I've also checked out llvm. Both are synced to r61075. I'm using Apple's gcc 4.0.1: $ gcc -v Using built-in specs. Target: i686-apple-darwin9 Configured with: /var/tmp/gcc/gcc-5488~2/src/configure --disable-checking -enable-werror --prefix=/usr --mandir=/share/man --enable-languages=c,objc,c++,obj-c++

...GNU install. We're talking about the -C option (uppercase). > The -C option is used directly in docs/Makefile. So the change will have > to go into docs/Makefile. Either that or upgrade install to version 5. docs/Makefile uses $(INSTALL) -C (uppercase). My point is that /usr/dcs/..../ginstall doesn't accept -C but /usr/bin/install does. Changing it in Makefile.config will do the trick. -- Misha Brukman :: http://misha.brukman.net :: http://llvm.cs.uiuc.edu

...#39;t really matter. What was happening is that http11 was not installing and the "require ''http11''" failed silently, and so the loading of mongrel.rb didn''t load completely (it stopped at that require). Http11 was not loading because there is no ''ginstall'' on my machine, it is called ''install'', and it is in a different place than expected. Anyway, fixing that up in the Makefile, running ''make clean'', then ''make'', then ''make install'' and the http11.bundle was insta...

...out the -C option (uppercase). > > > The -C option is used directly in docs/Makefile. So the change will have > > to go into docs/Makefile. Either that or upgrade install to version 5. > > docs/Makefile uses $(INSTALL) -C (uppercase). > > My point is that /usr/dcs/..../ginstall doesn't accept -C but > /usr/bin/install does. > > Changing it in Makefile.config will do the trick. You were advocating changing the INSTALL variable to use -c instead of -C, so in docs/Makefile the command: $(INSTALL) -C ... would be expanded as: /usr/bin/install -c -C ... wh...

...i get this error whether i use gnu-make of sun-make, see the error and reasons below. gmake[1]: Entering directory `/export/medusa/darin/build/R-2.3.0/etc' installing etc ... /bin/bash: -c: line 1: syntax error near unexpected token `;' /bin/bash: -c: line 1: `for f in ; do /opt/csw/bin/ginstall -c -m 644 ${f} "/export/home/darin/build/R-2.3.0/cswstage/opt/csw/lib/R/etc"; done' gmake[1]: *** [install] Error 2 gmake[1]: Leaving directory `/export/medusa/darin/build/R-2.3.0/etc' gmake: *** [install] Error 1 in etc/Makefile if i comment lines 60-62 make install continues...

...t, I just tried installing R 1.1.1 on SuSE 7.0 and encountered some problems. Using the precompiled binaries, I had a failed dependency: R was looking for "libblas.so.2" and apparently didn't find it. I then tried compiling from sources, which failed with the message: "/usr/bin/ginstall: zero.so No such file or directory" (or something to that effect). I'm using the Personal version of SuSE 7.0 so perhaps some important programs/files aren't included. Any suggestions would be greatly appreciated. Regards, Andy Bernat ________________________________________________...

...ectory `/usr/local/src/R-2.6.2/m4' gmake[1]: Entering directory `/usr/local/src/R-2.6.2/tools' gmake[1]: Nothing to be done for `install'. gmake[1]: Leaving directory `/usr/local/src/R-2.6.2/tools' gmake[1]: Entering directory `/usr/local/src/R-2.6.2/doc' installing doc ... /bin/ginstall: cannot change permissions of `/usr/local/lib/R/doc': No such file or directory mkdir /usr/local/lib/R/doc mkdir: Failed to make directory "/usr/local/lib/R/doc"; File exists gmake[1]: *** [installdirs] Error 2 gmake[1]: *** Waiting for unfinished jobs.... /bin/ginstall -c -m 644 ../N...

...$gho; + +sub prep () { + target_install_packages_norec($ho, qw(lvm2)); + + $gho= prepareguest($ho, $gn, $guesthost, 22, + $disk_mb, 40); + + prepareguest_part_lvmdisk($ho, $gho, $disk_mb); + + target_cmd_root($ho, "umount $gho->{Lvdev} ||:"); +} + +sub ginstall () { + my $arch= $r{"$gho->{Guest}_arch"}; + my $gsuite= guest_var($gho,''suite'',$c{GuestDebianSuite}); + my $di_ver= guest_var($gho,''diversion'',''current''); + + print("guest: $gho->{Guest}\n"); + print(&qu...

...nstall version 0.63.2 on an SGI Origin 200 with plenty of memory, running Irix 6.5. I previously installed 0.63.0 on this same system without incident. I'm getting the following error when I run ./configure: creating cache ./config.cache checking for a BSD compatible install... /usr/local/bin/ginstall -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... ratfor checking for latex... /usr/local/teTeX/bin/latex checking for dvips.../usr/local/teTeX/bin/dvips checking for makeindex... /usr/local/teTeX/bin/...

...roblem is already in 0.62.2 If I take yesterday's R-release.tar.gz (or also R-0.62.2.tar.gz) unpack and add CC=cc ----- to config.site, then ./configure ----------- it ends VERY badly: % ./configure creating cache ./config.cache checking for a BSD compatible install... /usr/local/bin/ginstall -c checking whether ln -s works... yes checking for ranlib... ranlib checking for bison... bison -y checking for ar... ar checking for ratfor... ratfor checking for latex... /afs/ethz.ch/public/teTeX/teTeX/bin/sparc-solaris2.5/latex checking for dvips... /afs/ethz.ch/public/teTeX/teTeX/bin/sparc-so...

...ross compiling... no checking for executable suffix... checking for object suffix... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking how to run the C preprocessor... gcc -E checking for a BSD compatible install... /usr/bin/ginstall -c checking for gcc option to accept ANSI C... none needed checking whether to include debugging symbols... yes checking for remsh... 0 checking for broken largefile support... yes checking ipv6 stack type... linux-glibc checking for library containing getaddrinfo... none required...

Hello, I couldn't help noticing that the debian build system in cvs was changed. As I used to compile and install from cvs, I discovered a small problem regarding autogen.sh. It's called in debian/rules, before the obj-dir is created (and changed into and ../configure is started). At least on my system autogen.sh implicitly runs ./configure, so the original source path is already

Hello -- Some wav files have been crashing the stuff I checked out from cvs last night. Is this happening to anyone else? Red Hat Linux release 7.3 (Valhalla) Kernel 2.4.18-5 on an i686 gcc-2.96-110 glibc-2.2.5-36 Encoding "04_imiuta.wav" to "04_imiuta.ogg" at quality 1.00 [100.0%] [ 0m00s remaining] \Segmentation fault Program received signal

...ables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ANSI C... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/ginstall -c checking whether ln -s works... yes checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for egrep... grep -E checking for ANSI C header files... yes checking for an ANSI C-conforming const... yes checking for debugging... yes checking for sys/types.h... yes checking for sys/sta...