All of lore.kernel.org
 help / color / mirror / Atom feed
From: ramsdell@mitre.org (John D. Ramsdell)
To: Jacob Gorm Hansen <jacobg@diku.dk>
Cc: xen-devel@lists.xensource.com, Grzegorz Milos <gm281@cam.ac.uk>
Subject: Re: [PATCH] Integrating applications into Mini-OS
Date: 15 May 2006 09:45:34 -0400	[thread overview]
Message-ID: <ogtu07rqu4h.fsf@divan.mitre.org> (raw)
In-Reply-To: <e08041f30605150518i6eeb4ce7gdb6dcf9bc9fd5643@mail.gmail.com>

"Jacob Gorm Hansen" <jacobg@diku.dk> writes:

> I have attached a small patch to mini-os which changes the mini-os
> Makefile and adds a dummy main function which you can override by
> linking with your own main() first, as in:

The primary goal of my patch is to change the Mini-OS sources so that
one need not modify source files in the Mini-OS distribution to add an
application.  I'm not wedded to the particulars of my patch, however,
your patch is insufficient for my goals.  You see, sometimes one wants
to build Mini-OS using the newlib C library, and sometimes one wants
to build Mini-OS so it uses only the subset of the C library that
comes with Mini-OS.  I really need #if !defined HAVE_LIBC preprocessor
commands to be added to lib/printf.c and lib/string.c.

John

  parent reply	other threads:[~2006-05-15 13:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-11 16:34 [PATCH] Integrating applications into Mini-OS John D. Ramsdell
2006-05-15 12:18 ` Jacob Gorm Hansen
2006-05-15 12:46   ` Ian Campbell
2006-05-15 13:08     ` Jacob Gorm Hansen
2006-05-15 13:20       ` Jacob Gorm Hansen
     [not found]       ` <ogtpsifqtkz.fsf@divan.mitre.org>
2006-05-15 14:40         ` Jacob Gorm Hansen
2006-05-15 14:45           ` John D. Ramsdell
2006-05-15 15:09           ` John D. Ramsdell
2006-05-15 15:15             ` Jacob Gorm Hansen
2006-05-15 13:45   ` John D. Ramsdell [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-15 13:33 Puthiyaparambil, Aravindh
2006-05-15 14:12 ` Jacob Gorm Hansen

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=ogtu07rqu4h.fsf@divan.mitre.org \
    --to=ramsdell@mitre.org \
    --cc=gm281@cam.ac.uk \
    --cc=jacobg@diku.dk \
    --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.