Re: Stubdom GMP build failure for gcc 6

[Wei Liu <wei.liu2@citrix.com>]

On Fri, Oct 28, 2016 at 01:50:36PM +0100, Wei Liu wrote:
> On Fri, Oct 28, 2016 at 06:29:49AM -0600, Jan Beulich wrote:
> > >>> On 28.10.16 at 14:10, <wei.liu2@citrix.com> wrote:
> > > There have been a few reports on stubdom build failure with gcc 6
> > > toolchain. I spent some time yesterday to figure what went wrong. Here
> > > is what I found.
> > > 
> > > When building GMP library, its configure script generates small C
> > > programs to determine various aspects of the system. Unfortunately the
> > > build rune for it is incorrect, so the test program ends up consuming
> > > newlib headers while linking against the host glibc. It's amazing that
> > > this even worked in the past few years! :-)
> > > 
> > > Unfortunately my attempt to fix it by providing LDFLAGS="-nostdlib
> > > -LXXX" doesn't work. It turns out that there is no crt generated in
> > > newlib. I'm not sure if that's because the newlib port is incomplete or
> > > I haven't discovered a way to teach it to generate one.
> > 
> > Considering that they can't reasonably try to run any of these
> > test programs (after all this is a cross build), wouldn't it suffice to
> > make up crt*.o just for the configure process, and just providing
> > the necessary symbols to make linking succeed? Agreed this, if
> > anything, makes the present situation even uglier, but it might
> > work.
> > 
> 
> It might. But that's not sustainable IMO.
> 
> One thing is that gmp configure doesn't try to run those test programs,
> because the configure rune doesn't indicate a cross-build, although it
> is actually one.

This is the key to fix this issue -- I didn't even notice it when I
wrote this down!

After going through its configure script options, I found a way to make
it aware of cross-compilation.

Wei.

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel