From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: Christoph Egger <Christoph.Egger@amd.com>,
xen-devel@lists.xensource.com,
Keir Fraser <keir.fraser@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] minios: minor buildsystem fixes
Date: Wed, 15 Jul 2009 13:24:21 -0400 [thread overview]
Message-ID: <20090715172421.GD4903@const.linuxsymposium.org> (raw)
In-Reply-To: <19037.64984.324031.106467@mariner.uk.xensource.com>
Hello,
Ian Jackson, le Wed 15 Jul 2009 17:03:36 +0100, a écrit :
> > The new infrastructure I have in mind will allow to choose if you use
> > newlib, libz, lwip and pciutils or use the native libs from the
> > base system.
>
> And certainly not the host operating system's libraries for our
> cross-build !
Yes, that's asking for problems.
> > NetBSD libc doesn't have linux integer types, that's why mini-os
> > has been moved to C99 integer types. The mini-os headers need
> > some re-structuring to not conflict with the native libc, namely
> > if you want a mini-os header you explicitely have to type
> > <mini-os/header.h>
>
> I agree that it would be good to replace the minios libc. The current
> libc is horrid. The BSD libc is very nice (and I have found it a joy
> to port to a new embedded target, in the past).
That should be fine yes. I don't remember precisely the reasons why I
chose newlib. I didn't know the BSD libc had embedded targets too.
> But if we change to a new libc this should be done by always using the
> new libc even on Linux hosts.
Yes. We should avoid having to fix several libcs.
Samuel
next prev parent reply other threads:[~2009-07-15 17:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-15 9:42 [PATCH] minios: minor buildsystem fixes Christoph Egger
2009-07-15 10:40 ` Keir Fraser
2009-07-15 12:27 ` Christoph Egger
2009-07-15 12:35 ` Stefano Stabellini
2009-07-15 12:39 ` Keir Fraser
2009-07-15 12:43 ` Stefano Stabellini
2009-07-15 12:59 ` Keir Fraser
2009-07-15 14:54 ` Christoph Egger
2009-07-15 16:03 ` Ian Jackson
2009-07-15 16:13 ` Stefano Stabellini
2009-07-15 17:24 ` Samuel Thibault [this message]
2009-07-16 12:17 ` Christoph Egger
2009-07-16 13:46 ` Samuel Thibault
2009-07-16 13:53 ` Ian Jackson
2009-07-15 16:39 ` Stefano Stabellini
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=20090715172421.GD4903@const.linuxsymposium.org \
--to=samuel.thibault@ens-lyon.org \
--cc=Christoph.Egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=stefano.stabellini@eu.citrix.com \
--cc=xen-devel@lists.xensource.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.