All of lore.kernel.org
 help / color / mirror / Atom feed
From: ramsdell@mitre.org (John D. Ramsdell)
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: xen-devel@lists.xensource.com, gm281@cam.ac.uk
Subject: Re: Mini-OS Makefile and Cross Compilation
Date: 03 Apr 2007 07:08:55 -0400	[thread overview]
Message-ID: <ogtejn11zqw.fsf@oolong.mitre.org> (raw)
In-Reply-To: <C237B09B.54F9%Keir.Fraser@cl.cam.ac.uk>

The command in my previous post should have been:

$ make CROSS_COMPILE=$HOME/opt/i386-elf/bin/i386-elf- TARGET_ARCH=x86_32

not this:

$ make CROSS_COMPILE=$HOME/opt/i386-elf/i386-elf/bin/ TARGET_ARCH=x86_32

This should allow the makefile to find the correct version of objcopy.

Keir Fraser <Keir.Fraser@cl.cam.ac.uk> writes:

> I doubt anyone has ever cross-compiled the minios. I'd suggest
> making its build system more like Xen's in terms of how it picks up
> the tool chain (Xen can be cross compiled). I have no specific
> pointers on how to do that.

Last summer, I cross-compiled a 32-bit minios for 32-bit Xen so that I
could build an application in the Lua scripting language.  The
interpreter required a C library, so I used newlib.

On a 32-bit machine, I can still build Mini-OS with a cross compiler
with:

$ make CROSS_COMPILE=$HOME/opt/cross/bin/i386-elf-

The problem seems to be when specifying a different target
architecture.  I also can no longer build a minios library to link
with the application, I'm not worried about that now.

By the way, the latest version of newlib, 1.15.0, no longer needs to
be patched for use with Mini-OS.

John

      reply	other threads:[~2007-04-03 11:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1HYSaT-0003Vz-5b@host-192-168-0-1-bcn-london>
2007-04-02 23:11 ` Mini-OS Makefile and Cross Compilation John D. Ramsdell
2007-04-03  6:19   ` Keir Fraser
2007-04-03 11:08     ` John D. Ramsdell [this message]

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=ogtejn11zqw.fsf@oolong.mitre.org \
    --to=ramsdell@mitre.org \
    --cc=Keir.Fraser@cl.cam.ac.uk \
    --cc=gm281@cam.ac.uk \
    --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.