> As DJ noted, configure in libssp is trying to create an executable > when building a cross-gcc.
Yes, I struck this recently myself. > What is the resolution: build with --disable-libssp (or add it to > the noconfigdirs list) or fix libssp/configure? The former will be far easier, unless you desparately want ssp support for your target. libssp's configure script checks for certain behaviour from vsnprintf and needs to run the test program to determine that. Ben
