From: "Ted Ts'o" <tytso@mit.edu>
To: Ext4 Developers List <linux-ext4@vger.kernel.org>,
xfs-oss <xfs@oss.sgi.com>
Subject: Build script for a hermetic build of xfstests
Date: Thu, 21 Jul 2011 19:54:41 -0400 [thread overview]
Message-ID: <20110721235441.GB25092@thunk.org> (raw)
With the six patches which I just sent (3 for xfsprogs, 3 for
xfstests), I'm now able to build xfstests hermetically using the
following script. It's still a bit rough, but I offer it up if anyone
else wants to be able to build xfstests without having to worry about
hidden dependencies in the distro-supplied /usr/include/xfs
directories, etc.
- Ted
#!/bin/bash -vx
DESTDIR=$(pwd)/bld
mkdir -p $DESTDIR
export CFLAGS="-I$DESTDIR/include"
export LDFLAGS="-static -L$DESTDIR/lib"
(cd e2fsprogs-libs; ./configure --prefix=/; make ; make DESTDIR=$DESTDIR install)
(cd attr; ./configure --prefix=$DESTDIR; make LLDFLAGS=-all-static ; make install-dev ; make install)
(cd acl; ./configure --prefix=$DESTDIR; make LLDFLAGS=-all-static; make install-dev; make install)
(cd libaio; make prefix=$DESTDIR install)
export DIST_ROOT=$DESTDIR
export LIBS=-lpthread
(cd xfsprogs-dev; make realclean ; make configure ; ./configure --prefix=/; make LLDFLAGS=-all-static BUILD_VERBOSE=1; make install; make install-dev)
unset LIBS
unset DIST_ROOT
export LIBTOOL="/usr/bin/libtool --tag=CC"
(cd dmapi; CFLAGS="-I$DESTDIR/include -L$DESTDIR/lib" LDFLAGS=-static ./configure --prefix=$DESTDIR; make LLDFLAGS=-all-static; make install-dev; make install)
unset LIBTOOL
find . -name \*.la | xargs rm -f # Die, libtool, die!!!!
cp $DESTDIR/include/xfs/dmapi.h $DESTDIR/include
set
export LIBS=-lpthread
export CFLAGS="-I$DESTDIR/include -fno-stack-protector"
(cd xfstests-dev; ./configure ; make LLDFLAGS=-all-static BUILD_VERBOSE=1)
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
reply other threads:[~2011-07-22 0:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110721235441.GB25092@thunk.org \
--to=tytso@mit.edu \
--cc=linux-ext4@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox