Unable to detect exception model on gcj-eabi-branch

Fri Aug 31 17:45:00 GMT 2007

Andrew Haley wrote:
> David Daney writes:
>> > 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.
>
It is linking the build system's /usr/lib/libasound.so instead of the 
version from the sysroot. Not good.
Daivd Daney