Unable to detect exception model on gcj-eabi-branch

Fri Aug 31 17:36:00 GMT 2007

David Daney writes:
 > Andrew Haley wrote:
 > > David Daney writes:
 > > > I am trying to build the gcj-eabi-branch and am getting this error while 
 > > > configuring in libjava:
 > > > 
 > > > checking for exception model to use... configure: error: unable to 
 > > > detect exception model
 > > > 
 > > > 
 > > > Configured like this:
 > > > 
 > > > ../gcj-eabi-branch/configure --target=armv5tl-montavista-linuxeabi 
 > > > --prefix=/home/daney/mvl/gcj 
 > > > --with-sysroot=/home/daney/mvl/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/target 
 > > > --enable-languages=c,c++,java --with-float=soft --disable-java-awt 
 > > > --without-x --disable-jvmpi --enable-__cxa_atexit
 > > > 
 > > > I will try again adding --disable-sjlj-exceptions, but I was hoping that 
 > > > it would work the other way [i686|x86_64|mips|mips64]-linux do not 
 > > > require any special exception specifiers.
 > > 
 > > I used options 
 > > 
 > > " '--with-system-zlib' '--enable-threads=posix' '--enable-nls'
 > > '--enable-__cxa_atexit' '--enable-clocale=gnu'
 > > '--enable-libstdcxx-debug' '--enable-mpfr' '--enable-checking=release'
 > > '--disable-multilib' '--disable-static' 'arm-linux-gnueabi'
 > > '--disable-sjlj-exceptions' '--prefix=/home/aph/gcc/install'
 > 
 > Yes, the --disable-sjlj-exceptions seems to be required. I wonder why 
 > it is not the default.
I'm not sure, but I'm not massively concerned.
 > Also is --enable-threads=posix required? One would think that would be 
 > the default as well.
I always use --enable-threads or --enable-threads=posix. It didn't
used to be the defaul; maybe it now is, but that's force of habit.
 > In any event, I get much further in the build now. My current problem 
 > is that it is trying to link the JNI alsa library against the build 
 > host's libraries. Bad Classpath, bad. :
 > 
 > libtool: link: /home/daney/gccsvn/arm-gcj-eabi-branch/./gcc/xgcc 
 > -B/home/daney/gccsvn/arm-gcj-eabi-branch/./gcc/ 
 > -B/home/daney/mvl_ti/gcj/armv5tl-montavista-linuxeabi/bin/ 
 > -B/home/daney/mvl_ti/gcj/armv5tl-montavista-linuxeabi/lib/ -isystem 
 > /home/daney/mvl_ti/gcj/armv5tl-montavista-linuxeabi/include -isystem 
 > /home/daney/mvl_ti/gcj/armv5tl-montavista-linuxeabi/sys-include -shared 
 > .libs/gnu_javax_sound_midi_alsa_AlsaMidiSequencerDevice.o 
 > .libs/gnu_javax_sound_midi_alsa_AlsaPortDevice.o 
 > .libs/gnu_javax_sound_midi_alsa_AlsaMidiDeviceProvider.o 
 > /usr/lib/libasound.so -ldl -lm -lpthread -Wl,-soname 
 > -Wl,libgjsmalsa.so -o .libs/libgjsmalsa.so
 > /usr/lib/libasound.so: could not read symbols: File in wrong format
What's the problem? Is the file really in a different format? If so,
why? I certainly don't get this.
Andrew.