Date: Sat, 20 Dec 1997 19:14:09 -0800 From: "Jordan K. Hubbard" <jkh@time.cdrom.com> To: current@freebsd.org Subject: -current release build is broken (last 3 days) Message-ID: <16095.882674049@time.cdrom.com>
next in thread | raw e-mail | index | archive | help
===> lib/libcom_err/doc install-info --defsection="Programming & development tools." --defentry="* libc om_err: (com_err). A Common Error Description Library for UNIX." com_err .info /R/stage/trees/bin/usr/share/info/dir install -c -o bin -g bin -m 444 com_err.info.gz /R/stage/trees/bin/usr/share/in fo ===> lib/libcom_err/doc cd /usr/src/lib/libcom_err/doc ; make install DESTDIR=/R/stage/trees/info SHARED =copies make: don't know how to make /R/stage/trees/info/usr/share/info/dir. Stop *** Error code 2 Stop. *** Error code 1 Which brings up a point (was it Satoshi who was last fooling with this?) - shouldn't there be some way of dealing with this dependancy on a dir file? When's the right time to install it, if so much depends on it, or should a version be created on demand? If on demand, what goes in it and how do you guarantee consistent results? If not, when's the best time to create the prototype? It'd have to be fairly early, to prevent the above from happening. I can think of a couple of quick-fix solutions to this one, in any case, but would prefer to make the right one. ;) Comments? Jordan
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?16095.882674049>