Date: Sun, 14 Mar 1999 23:01:14 -0800 From: Ludwig Pummer <ludwigp@bigfoot.com> To: Leo Kliger <leo@astea.com.au> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: where's BASH Message-ID: <4.1.19990314225658.00ab12a0@mail-r> In-Reply-To: <Pine.BSO.4.10.9903142141530.3879-100000@berkeleycs.ml.org> References: <199903150551.QAA05272@astea.com.au>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:43 PM 3/14/99 , Spam Me Here wrote: >It isn't installed by default, go to /usr/ports/shells/bash2, >and ( as root ) type > >make ; make install ; make clean I've found that with any kind of command line involving multiple makes which depend on the previous, && is preferable to ;, so the line would be make && make install && make clean This way, if make or make install fail, make won't clean up its progress so far. Could you imagine what would happen if you did a make clean following every hiccup of installing the KDE port? Or (speaking from personal experience) you were building your first 3.1-S kernel where you had previously made 2.2.8 kernels... the make depend fails... the 2.2.8 kernel (left over from earlier) gets installed... the next reboot brings a nasty surprise. Moral of story: use && instead of ; --Ludwig Pummer ( ludwigp@bigfoot.com ) ICQ UIN: 692441 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4.1.19990314225658.00ab12a0>