From: Wei Liu <wei.liu2@citrix.com>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: jgross@suse.com, xuquan8@huawei.com,
Wei Liu <wei.liu2@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 14:36:04 +0100 [thread overview]
Message-ID: <20161028133604.GH30231@citrix.com> (raw)
In-Reply-To: <22547.21210.590425.654624@mariner.uk.xensource.com>
On Fri, Oct 28, 2016 at 02:30:02PM +0100, Ian Jackson wrote:
> Wei Liu writes ("Stubdom GMP build failure for gcc 6"):
> > 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.
>
> How does stubdom link its actual final program, without a crt0 ?
>
It chdir to mini-os and uses linker script provided there.
> Can we not just reproduce its link line somehow ?
>
I don't think that would result in a program that can run on Linux.
Wei.
> Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-28 13:36 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 [this message]
2016-10-28 15:42 ` Ian Jackson
2016-10-28 14:44 ` Juergen Gross
2016-10-28 15:38 ` Wei Liu
-- 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=20161028133604.GH30231@citrix.com \
--to=wei.liu2@citrix.com \
--cc=dgdegra@tycho.nsa.gov \
--cc=ian.jackson@eu.citrix.com \
--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).