Alexander Leidinger wrote:
> It's not in configure.in because autoconf is responsible for this. grep
> through configure and you will see it.
I see. Nevertheless, even when I had the effects reported, the string
cross_compiling was not set to "yes" (the warning was not displayed that
was supposed to). Or maybe it was not supposed to, as I was compiling
for i386 on an i386. But then why did it renamname the executable to
i386-redhat-linux-lame? I don't get it :(
> Some of the optimization stuff in configure.in depends on it.
I see.
> Can you please test the CVS version of LAME with the attached patch
> (I've no gcc 3.1 at the moment)?
Results are not good:
./configure
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets ${MAKE}... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for style of include used by make... GNU
checking for ranlib... ranlib
checking for gcc... gcc
checking for C compiler default output... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking dependency style of gcc... gcc3
checking for ld used by GCC... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
loading cache /dev/null within ltconfig
ltconfig: you must specify a host type if you use `--no-verify'
Try `ltconfig --help' for more information.
configure: error: libtool configure failed
But it passes this point if I supply a build target, e.g.
./configure i386-redhat-linux
but then comes:
checking for additional optimizations... ./configure: line 12362: syntax
error near unexpected token `;'
./configure: line 12362: ` ;;'
which reflects to the following lines in configure.in (around line 694):
*)
OPTIMIZATION="${OPTIMIZATION} -fdelayed-branch"
;;
esac
;;
I don't see what's wrong here at first glance :(
Akos
_______________________________________________
mp3encoder mailing list
[EMAIL PROTECTED]
http://minnie.tuhs.org/mailman/listinfo/mp3encoder
