From: Christoph Egger <Christoph.Egger@amd.com>
To: xen-devel@lists.xensource.com
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Keir Fraser <keir.fraser@eu.citrix.com>,
Stefano Stabellini <stefano.stabellini@eu.citrix.com>
Subject: Re: [PATCH] minios: minor buildsystem fixes
Date: Thu, 16 Jul 2009 14:17:20 +0200 [thread overview]
Message-ID: <200907161417.21029.Christoph.Egger@amd.com> (raw)
In-Reply-To: <19037.64984.324031.106467@mariner.uk.xensource.com>
On Wednesday 15 July 2009 18:03:36 Ian Jackson wrote:
> Christoph Egger writes ("[Xen-devel] [PATCH] minios: minor buildsystem
fixes"):
> > Attached patch changes MiniOS.mk and tools/Rules.mk
> > use the OS settings we build on.
>
> I don't think that's right. The minios cross-build should use the Xen
> cross build machinery. That machinery isn't very good but it is the
> same on every host.
It's not the same on every host due to lack of proper abstraction.
> Christoph Egger writes ("Re: [Xen-devel] [PATCH] minios: minor buildsystem
fixes"):
> > The current approach works for Linux only.
>
> Really ? What's wrong with it for NetBSD ?
Assumptions which don't apply to NetBSD.
> > NetBSD's base system is designed for cross-building.
>
> I don't think we should be trying to use the host operating system's
> cross-build support.
Please explain why not.
It's a question of having a proper abstraction.
> > 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 !
Please explain why not.
It's a question of having a proper abstraction.
> > Linux build will default to first, NetBSD build will default to latter
> > one.
>
> In particular I think this is quite wrong.
Please explain why.
> > 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).
>
> But if we change to a new libc this should be done by always using the
> new libc (BSD-derived, but not necessarily NetBSD; FreeBSD is another
> choice) even on Linux hosts.
I think, let's first find a proper abstraction and then make the decision what
is best for which host.
Christoph
--
---to satisfy European Law for business letters:
Advanced Micro Devices GmbH
Karl-Hammerschmidt-Str. 34, 85609 Dornach b. Muenchen
Geschaeftsfuehrer: Thomas M. McCoy, Giuliano Meroni
Sitz: Dornach, Gemeinde Aschheim, Landkreis Muenchen
Registergericht Muenchen, HRB Nr. 43632
next prev parent reply other threads:[~2009-07-16 12:17 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
2009-07-16 12:17 ` Christoph Egger [this message]
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=200907161417.21029.Christoph.Egger@amd.com \
--to=christoph.egger@amd.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=keir.fraser@eu.citrix.com \
--cc=samuel.thibault@ens-lyon.org \
--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.