search for: mkinstalldirs

Whoops, missed a ./mkinstalldirs. Correct patch to Makefile.in is attached. -- Edward S. Marshall <emarshall at mercantec.com> UNIX Administrator http://www.nyx.net/~emarshal/ Mercantec, Inc. -------------- next part -------------- 24c24 < CFLAGS=@CFLAGS@ $(PATHS) @DEFS@...

...-------------------------------------------------------------- [ Felix qui potuit rerum cognoscere causas. ] -------------- next part -------------- 24c24 < CFLAGS=@CFLAGS@ $(PATHS) @DEFS@ --- > CFLAGS=@CFLAGS@ $(PATHS) @DEFS@ -I at top_srcdir@ -I. 28a29 > MKINSTALLDIRS=@srcdir@/mkinstalldirs 121,125c122,126 < ./mkinstalldirs $(DESTDIR)$(bindir) < ./mkinstalldirs $(DESTDIR)$(sbindir) < ./mkinstalldirs $(DESTDIR)$(mandir) < ./mkinstalldirs $(DESTDIR)$(mandir)/$(mansubdir)1 < ./mkinstalldirs $(DESTDIR)$(mandir)/$(mansubdir)8 --- > $(MKINSTALL...

...LVM_OBJ_ROOT)/Makefile.common that have line: include $(LLVM_OBJ_ROOT)/Makefile.config (also $(LLVM_OBJ_ROOT)/Makefile.config used in llvm-test/Makefile.config.in) and llvm/Makefile.config.in have lines: INSTALL_SH := $(LLVM_SRC_ROOT)/autoconf/install-sh MKDIR := $(LLVM_SRC_ROOT)/autoconf/mkinstalldirs But all this projects (LLVM, Stacker, sample, llvm-java) have autoconf/install-sh and autoconf/mkinstalldirs in own sources. I think at building, for example, llvm-java use llvm-java/autoconf/install-sh is more correct (synchronized version with other autoconf files and configure in project sourc...

...rom an NFS server with maproot=nobody, this fails. Aside from that problem, there may be a larger problem that ssh is running with euid=0 when it doesn't need to be. Thanks, -Fred Summary: Makefile.in: - OpenSSH doesn't build well if you are building outside of the source tree. - mkinstalldirs lives in $(srcdir), not necessarily '.'. - fixprogs lives in $(srcdir), not necessarily '.'. - Separate CFLAGS from CPPFLAGS, so one can override CFLAGS from the command line without whacking include paths. configure.in: - Find OpenSSL install as a framework. (-framework...

...3.8.27-1.src.rpm so that I may use it on my CentOS 5 box, but it fails with the following errors <snip> + make MAKEPACKAGE=YES if [ "UTILS" = po ] ; then \ for i in po/Makefile* ; do \ if [ -f "$i" ] ; then \ if grep '^mkinstalldirs.*=.*case' $i ; then \ echo "fixing broken $i which causes wrong path to mkinstalldirs to be used"; \ perl -spi -e 's:^mkinstalldirs\s*=\s*.*:mkinstalldirs = \$(SHELL) \$(MKINSTALLDIRS):' $i; \ fi \...

Personally, I don't think LLVM projects should need much in the way of autoconf stuff. They certainly don't need to replicate things like install-sh and mkinstalldirs. I'd vote for taking these out of the projects rather than making the makefiles deal with them. I think in most cases these are just historical artifacts that have been with the projects since long before the new Makefile.rules of last fall. More below .. On Mon, 2005-02-14 at 15:40, Vladimi...

...-with-llvmobj=~/Documents/research/llvm/llvm-2.0/ (I've tried all of those with and without / at the end of the lines). The error it reports is below. Any ideas what is causing this? Thanks, Ben Chambers Error Report: ./config.status: line 1044: ~/Documents/research/llvm/llvm-2.0//autoconf/mkinstalldirs: No such file or directory~/Documents/research/llvm/llvm-2.0//autoconf/install-sh: ~/Documents/research/llvm/llvm-2.0//autoconf/install-sh: No such file or directoryconfig.status: executing lib/Makefile commands./config.status: line 1046: ~/Documents/research/llvm/llvm-2.0//autoconf/mkinstalldirs:...

On Mon, 14 Feb 2005, Reid Spencer wrote: > Personally, I don't think LLVM projects should need much in the way of > autoconf stuff. They certainly don't need to replicate things like > install-sh and mkinstalldirs. I'd vote for taking these out of the > projects rather than making the makefiles deal with them. I think in > most cases these are just historical artifacts that have been with the > projects since long before the new Makefile.rules of last fall. I agree. >> llvm/Makefile.conf...

Ben, I am trying to create a package for Openssh.3-1p1, but the /contrib/solaris/buildpkg.sh script failes with the following errors: ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/b in mkdir /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/bin ./mkinstalldirs /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/s bin mkdir /tools/OpenSSH/openssh-3.1p1/contrib/solaris/package/usr/local/sbin...

....orig Fri Jun 22 09:53:07 2001 +++ Makefile.in Fri Jun 22 09:56:17 2001 @@ -164,15 +164,17 @@ distprep: catman-do autoreconf -install: $(TARGETS) install-files host-key +install: $(TARGETS) install-dirs install-prog install-man install-conf host-key -install-files: +install-dirs: $(srcdir)/mkinstalldirs $(DESTDIR)$(bindir) $(srcdir)/mkinstalldirs $(DESTDIR)$(sbindir) $(srcdir)/mkinstalldirs $(DESTDIR)$(mandir) $(srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/$(mansubdir)1 $(srcdir)/mkinstalldirs $(DESTDIR)$(mandir)/$(mansubdir)8 $(srcdir)/mkinstalldirs $(DESTDIR)$(libexecdir) + +install-prog:...

On Mon, 2005-02-14 at 20:53, Chris Lattner wrote: > On Mon, 14 Feb 2005, Reid Spencer wrote: > > > Personally, I don't think LLVM projects should need much in the way of > > autoconf stuff. They certainly don't need to replicate things like > > install-sh and mkinstalldirs. I'd vote for taking these out of the > > projects rather than making the makefiles deal with them. I think in > > most cases these are just historical artifacts that have been with the > > projects since long before the new Makefile.rules of last fall. > > I agree. Ok...

Hi, When I am trying to update openSSH using openssl-1.0.1i.It is giving issues. ./mkinstalldirs /home/epooshi/x86/openssh/openssh-5.2p1//libexec mkdir /home/epooshi/x86/openssh/openssh-5.2p1/libexec (umask 022 ; ./mkinstalldirs /var/empty) mkdir /var/empty mkdir: Failed to make directory "/var/empty"; Permission denied *** Error code 2 make: Fatal error: Command failed for target `i...

kjoonlee@blacksun:~/xiph/vorbis-tools$ make install Making install in po make[1]: Entering directory `/home/kjoonlee/xiph/vorbis-tools/po' /bin/sh `case "./mkinstalldirs" in /*) echo "./mkinstalldirs" ;; *) echo ".././mkinstalldirs" ;; esac` /home/kjoonlee/share /bin/sh: .././mkinstalldirs: No such file or directory make[1]: *** [install-data-yes] Error 127 make[1]: Leaving directory `/home/kjoonlee/xiph/vorbis-tools/po' make: *** [inst...

...make install-pdf Everything works fine apart from "make install-info": --------------------------------------------------------------------- [root@fyb012000002 /home/DOWNLOADS/R/Rdev]# make install-info make[1]: Entering directory `/home/DOWNLOADS/R/Rdev/doc/manual' Usage: mkinstalldirs [-h] [--help] [-m mode] dir ... make[1]: *** [/usr/local/lib/Rdevel/info/dir] Error 1 make[1]: Leaving directory `/home/DOWNLOADS/R/Rdev/doc/manual' make: [install-info] Error 2 (ignored) ---------------------------------------------------------------------- This happens from R-1.2.3 (and prev...

...dParty/build_apal" install (cd openbsd-compat && make) make[1]: Entering directory `/home/mpal/ws2/dawn_v1/3dParty/openssh-5.9p1/openbsd-compat' make[1]: Nothing to be done for `all'. make[1]: Leaving directory `/home/mpal/ws2/dawn_v1/3dParty/openssh-5.9p1/openbsd-compat' ./mkinstalldirs /home/mpal/ws2/dawn_v1/3dParty/build_apal/bin ./mkinstalldirs /home/mpal/ws2/dawn_v1/3dParty/build_apal/sbin ./mkinstalldirs /home/mpal/ws2/dawn_v1/3dParty/build_apal/man ./mkinstalldirs /home/mpal/ws2/dawn_v1/3dParty/build_apal/man/man1 ./mkinstalldirs /home/mpal/ws2/dawn_v1/3dParty/build_apal/man...

...BOSE=1 for dir in lib/Support lib/TableGen utils lib/IR lib tools/llvm-config tools runtime docs unittests; do \ if ([ ! -f $dir/Makefile ] || \ command test $dir/Makefile -ot /home/csabaraduly/workspace/LLVM/llvm/$dir/Makefile ); then \ /home/csabaraduly/workspace/LLVM/llvm/autoconf/mkinstalldirs $dir; \ /bin/cp /home/csabaraduly/workspace/LLVM/llvm/$dir/Makefile $dir/Makefile; \ fi; \ (make -C $dir all ) || exit 1; \ done make[1]: Entering directory `/home/csabaraduly/workspace/LLVM/build-clang/lib/Support' make[1]: Nothing to be done for `all'. make[1]: Leaving directo...

Basically all platforms have a proper "mkdir -p". Autoconf has install-sh as fallback when using AC_PROG_MKDIR_P, which is also hardened against races if it is recent enough. Update that script and use MKDIR_P whereever possible. Installs fine in my tests and avoids the "mkdir: cannot create directory '?': File exists" messages along the way. Greetings, Eike --

[qali at qali test-suite]$ make VERBOSE=1 if [ ! -f SingleSource/Makefile ]; \ then \ /home/qali/Src/llvm-2.8/autoconf/mkinstalldirs SingleSource; \ cp /home/qali/Src/llvm-2.8/projects/test-suite/SingleSource/Makefile SingleSource/Makefile; \ fi; \ make -C SingleSource all make[1]: Entering directory `/home/qali/build/llvm-2.8-rev/projects/test-suite/SingleSource' if [ ! -f UnitTests/Makefile ]; \ then \ /home/qali/Src/llvm-...

...nu) libcurl/7.12.0 OpenSSL/0.9.7a zlib/1.1.4 Protocols: ftp gopher telnet dict ldap http file https ftps make install output: Making install in lib make[1]: Entering directory `/usr/src/libtheora-1.0alpha4/lib' make[2]: Entering directory `/usr/src/libtheora-1.0alpha4/lib' /bin/sh ../mkinstalldirs /usr/local/lib /bin/sh ../libtool --mode=install /usr/bin/install -c libtheora.la /usr/local/lib/libtheora.la /usr/bin/install - c .libs/libtheora.so.0.1.0 /usr/local/lib/libtheora.so.0.1.0 (cd /usr/local/lib && rm -f libtheora.so.0 && ln -s libtheora.so.0.1.0 libtheora.so.0) (c...

...ult configs) Below, there is full output of make: >> make VERBOSE=1 for dir in lib tools; do \ if ([ ! -f $dir/Makefile ] || \ command test $dir/Makefile -ot /home/username/dev/llvm/src/projects/test/$dir/Makefile ); then \ /home/username/dev/llvm/src/projects/test/build/../autoconf/mkinstalldirs $dir; \ /usr/bin/cp /home/username/dev/llvm/src/projects/test/$dir/Makefile $dir/Makefile; \ fi; \ (make -C $dir all ) || exit 1; \ done make[1]: Entering directory `/home/username/dev/llvm/src/projects/test/build/lib' for dir in sample; do \ if ([ ! -f $dir/Makefile ] || \ comm...