Pierre Labastie wrote:
On 30/10/2015 14:24, Michael Havens wrote:
tar xf gettext-0.19.5.1.tar.xz
cd gettext-0.19.5.1
cd gettext-tools
EMACS="no" ./configure --prefix=/tools --disable-shared
( make -C gnulib-lib 2>&1 | tee ../5.23.make.gnulib-lib.log && exit
$PIPESTATUS ) && echo GOOD
[...]
When you run the "make -C ... | tee ../something.log" command, your working
directory is /sources/gettext-0.19.5.1/gettext-tools. The "-C" does not change
that (only for running make), but ".." is /sources/gettext-0.19.5.1. So I
guess you might find your logs there. Note that if you loose them, you can
find them with...find:
find /sources -name \*.log -print
In my scripts I specify the directory explicitly. I use variations of:
DIR=`pwd`
PROGRAM=nmap-6.47
LOG=$DIR/$PROGRAM.log
BUILDDIR=/tmp/nmap
#DEST=$BUILDDIR/install
#SUDO=
rm -f $LOG
rm -rf $BUILDDIR
mkdir $BUILDDIR
cd $BUILDDIR
tar -xf $DIR/$PROGRAM.tar.?z* || exit 1
cd $PROGRAM
{
./configure ... &&
make &&
$SUDO make DESTDIR=$DEST install
} 2>&1 | tee -a $LOG
-- Bruce
--
http://lists.linuxfromscratch.org/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
Do not top post on this list.
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
http://en.wikipedia.org/wiki/Posting_style
