Olivier Galibert <galibert(a)pobox.com&gt; writes: Uhm, sorry, no offence intended, maybe I misunderstood yur advice. I admit, I have never seen (or heard of) the above symptoms/bug, so maybe I shouldn't have commented. It's just that I feel that it's dangerous to have a separate set of required configure switches for each build environment. I remember the last time Georg tried builds on 2.7 (64bit I think). He got weird crashes (which I (but apparently nobody else) could reproduce on 2.6). Somebody remarked that he had no problems on Solaris when using 'some-combination-of-uniontype-minimal-tagbits-whatever' which proved true for Georg (and me) as well. We could very well have left it at that, but there was still a bug in XEmacs which I finally tracked down. If we find some kind of reproducable problem/crash we should IMHO track it down and not try to find some configure incantation to cover it up. (Actually I think we already had this debate some time ago). IMHO (reproducible) core dumps are the best thing for the developers. If we suspect a compiler bug, we should try to pinpoint it and contact the vendor. If this was indeed the plan, I apologize and stay out of this debate with my 'smart remarks' :-) In this special case I was hoping, if it was really a compiler bug, Charles was in a much better position to get it fixed than any of us. Gunnar