xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Wei Liu <wei.liu2@citrix.com>
To: Juergen Gross <jgross@suse.com>
Cc: xuquan8@huawei.com, Wei Liu <wei.liu2@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	samuel.thibault@ens-lyon.org,
	Xen-devel <xen-devel@lists.xenproject.org>,
	dgdegra@tycho.nsa.gov
Subject: Re: Stubdom GMP build failure for gcc 6
Date: Fri, 28 Oct 2016 16:38:45 +0100	[thread overview]
Message-ID: <20161028153845.GL30231@citrix.com> (raw)
In-Reply-To: <72113d2b-153a-80f3-9587-63cea16938de@suse.com>

On Fri, Oct 28, 2016 at 04:44:10PM +0200, Juergen Gross wrote:
> On 28/10/16 14:10, Wei Liu wrote:
> > Hi all
> > 
> > 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.
> > 
> > So what should we do with this? I'm not sure if I can come up with a
> > non-intrusive patch quickly.  GMP is only used by tpm emulator, so for
> > the imminent 4.8 release I can write a patch to disable building that.
> > 
> > Ultimately we need to have a proper solution, because there can be other
> > breakages in the future. And I do wish users who need tpm emulator can
> > continue to use it. I don't have a clear answer as to how many people
> > care about this and how can we fix it.
> > 
> > Thoughts?
> 
> I just tried to verify it is working (or failing) for me. On the machine
> I normally did my Xen builds cmake was missing so it never tried to
> build libgmp. After installing it I saw the following problem:
> 
> at the end of libgmp build:
> Libraries have been installed in:
>    /home/gross/xen/stubdom/cross-root-x86_64/x86_64-xen-elf/lib64
> 
> and when trying to link stubdom-vtpm:
> make[2]: Entering directory '/home/gross/xen/extras/mini-os-remote'
> ld -r -d -nostdlib
> -L/home/gross/xen/stubdom/cross-root-x86_64/x86_64-xen-elf/lib  -m
> elf_x86_64 -\( /home/gross/xen/stubdom/vtpm/vtpm.a -T app.lds -\) -ltpm
> -ltpm_crypto -lgmp -lpolarssl --undefined main -o
> /home/gross/xen/stubdom/mini-os-x86_64-vtpm/mini-os_app.o
> ld: cannot find -lgmp
> 
> manually adding
> "-L/home/gross/xen/stubdom/cross-root-x86_64/x86_64-xen-elf/lib64" lets
> the link command succeed.
> 

This is a different issue from the one I report here.

But both stems from the fact that we don't really create a complete
cross-compile toolchain for stubdom, but piggy-back on the host
toolchain.

Presumably you didn't see my issue because you're using an older version
of glibc.

Wei.

> 
> Juergen

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

  reply	other threads:[~2016-10-28 15:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-28 12:10 Stubdom GMP build failure for gcc 6 Wei Liu
2016-10-28 12:29 ` Jan Beulich
2016-10-28 12:50   ` Wei Liu
2016-10-28 12:56     ` Jan Beulich
2016-10-28 12:59       ` Wei Liu
2016-10-29 17:19     ` Wei Liu
2016-10-28 13:30 ` Ian Jackson
2016-10-28 13:36   ` Wei Liu
2016-10-28 15:42     ` Ian Jackson
2016-10-28 14:44 ` Juergen Gross
2016-10-28 15:38   ` Wei Liu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-10-29  5:16 Pry Mar
2016-10-29 17:28 ` Wei Liu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20161028153845.GL30231@citrix.com \
    --to=wei.liu2@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=dgdegra@tycho.nsa.gov \
    --cc=jgross@suse.com \
    --cc=samuel.thibault@ens-lyon.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xuquan8@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).