From: Lele Ma <lelema.cn@gmail.com>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>,
xen-devel <xen-devel@lists.xen.org>
Subject: Re: [Help] How to build mini-OS with libc support, like Newlib?
Date: Tue, 2 Sep 2014 17:36:36 +0800 [thread overview]
Message-ID: <CADxFM8vcduXtvKv1d09wdfgh1oRT_afeok73KVdLi6+FKca7tQ@mail.gmail.com> (raw)
In-Reply-To: <20140902074756.GA3779@type.bordeaux.inria.fr>
On Tue, Sep 2, 2014 at 3:47 PM, Samuel Thibault
<samuel.thibault@ens-lyon.org> wrote:
>
> Lele MA, le Tue 02 Sep 2014 15:20:32 +0800, a écrit :
> > If Newlib can be used to build mini-os, how to do it? Do I have to compile a
> > cross-compiler first?
>
> Yes. But this all already handled by the Makefile in stubdom/, and see
> the end of README about the c-stubdom target which builds the c/
> directory.
>
Thank you so much! It is great to build newlib so conveniently. But
when I run 'make c-stubdom' in stubdom/, it yields:
make: *** No rule to make target `mini-os-x86_64-c', needed by
`c-stubdom'. Stop"
Do you have any idea about how this happen?
BTW, after building xen, there is a new directory named
"newlib-x86_64/' in stubdom/. I am a newbie to newlib and don't know
what's this exactly. Is it the newlib that a stubdomain can use as the
libc?
My xen version is 4.4.0 and dom-0 is Ubuntu-12.04. Thank you for your patience!
Best regards,
Lele MA
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2014-09-02 9:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 7:20 [Help] How to build mini-OS with libc support, like Newlib? Lele MA
2014-09-02 7:47 ` Samuel Thibault
2014-09-02 9:36 ` Lele Ma [this message]
2014-09-02 10:55 ` Samuel Thibault
2014-09-05 8:40 ` Lele MA
2014-09-06 9:54 ` Samuel Thibault
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=CADxFM8vcduXtvKv1d09wdfgh1oRT_afeok73KVdLi6+FKca7tQ@mail.gmail.com \
--to=lelema.cn@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xen.org \
/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).