RE: Problem building si for s390x

> >> > Segmentation fault
> >> 
> >> This is the first time the compiled glibc is invoked. 
> >> It means that you created a glibc that is miscompiled 
> >> or not compatible to the one you have in your system.

> > Interesting.  There's a glibc compiled for phase2 which
> > is used heavily.  The one that's built for phase3,
> > which is installed to an alternate location, is the
> > one that's failing.  I wonder what's different....
> 
> So do I.  Do you configure it with the same options besides the
> location?

Hmmm, the configure is the same, but there's a pre-configure
incantation that I don't recall seeing that exists in
the phase2, but not the phase3 setup.  By the time phase3
runs, of course, there IS a glibc in place, and it's being
used by the tools.  This is the only thing I can see that's
different. This is set before configure is called:

		<!-- glibc's config.guess needs to know something about
glibc,
                     even though we haven't built one yet.  Fake it. -->
		<setenv>
			<variable>ac_cv_prog_cc_stdc</variable>
			<value></value>
			<variable>ac_cv_prog_CPP</variable>
			<value>gcc -E</value>
			<variable>MSGFMT</variable>
			<value>/bin/true</value>
		</setenv>

		<!-- this is also needed for configure -->
		<execute>
			<command>touch</command>
			<param>/usr/include/limits.h</param>
		</execute>