search for: msg00131

Can someone provide instructions and the necessary environment/toolchain support needed to get Xen to build and boot on a native EFI system (i.e. with no CSM/legacy support)? Joe

I am putting the finishing touches on the next release. I got everything mostly working with the latest autotools, but I've noticed that the generated libtool after configure does not have $SED defined. searching around it seems to be a common problem. I thought as a simple workaround that I would just distribute a libtool script that sets $SED to 'sed' (expecting it to be in the

...dev/2007-September/002384.html -# -# Also watchout, if you replace ltmain.sh, there is a bug in some -# versions of libtool (or maybe autoconf) on some platforms where the -# configure-generated libtool does not have $SED defined. See also: -# -# http://lists.gnu.org/archive/html/libtool/2003-11/msg00131.html - -package="flac" - -olddir=`pwd` -srcdir=`dirname $0` -test -z "$srcdir" && srcdir=. - -cd "$srcdir" -DIE=0 - -ACLOCAL_FLAGS="-I m4 $ACLOCAL_FLAGS" - -echo "checking for autoconf... " -(autoconf --version) < /dev/null > /dev/null...

This patch series modernizes various aspects of the autotools based build system. There is a lot more that could and should be done, but I tried to stay conservative for now and just resolve some of the most obvious issues. Max Horn (5): configure: replace XIPH_C_FIND_ENDIAN by AC_C_BIGENDIAN autogen.sh: replace this by a simple call to autoreconf configure: always print