"Neil Jerram": > >> > >> What exactly do you mean here? (My guess: that you compiled and ran > >> the test program by hand, and that the exit status was 1 in each > >> case?) > > > > Yes, that's what I meant. > > Thanks. So, do you agree that my interpretation of what _should_ > happen is correct, and that we are therefore looking for a bug > somewhere that can cause a non-zero exit status to map to > SCM_I_GSC_STACK_GROWS_UP=1 ? > > Possibilities.... > > - The compiler. Is it possible that your compiler doesn't map the arg > of exit(...) to the exit status that the shell sees? > > - ./configure code. Is there a bug in the ./configure code that > confuses the exit status on some platforms only? Are you still using > the ./configure that came with Guile 1.8.5, or have you regenerated > it? If the latter, the bug could be being introduced by different > versions of the autotools than the ones we used upstream. > > I wish I could reproduce this myself, so I could investigate in > detail! I've downloaded the Debian package source (for > guile-1.8-1.8.5+1), and built it on an ia64 machine, and I don't see > the problem. I've attached my ./configure - can you check that it is > the same as the one in the official Debian build (in case I've made a > mistake with the patching process)? >
If using Ubuntu, things like that might very well happen because of their crazy dash stunt. (/bin/sh is not bash on Unbuntu, but a smaller shell called dash !)
