linux-um archives
 help / color / mirror / Atom feed
From: Dan Aloni <da-x@gmx.net>
To: Jeff Dike <jdike@addtoit.com>
Cc: User-mode Linux Kernel Development
	<user-mode-linux-devel@lists.sourceforge.net>
Subject: Re: [uml-devel] Problem with UML cross compilation
Date: Sun, 19 Oct 2003 22:28:25 +0200	[thread overview]
Message-ID: <20031019202825.GA10810@callisto.yi.org> (raw)
In-Reply-To: <200310191716.h9JHGZdb011736@ccure.karaya.com>

On Sun, Oct 19, 2003 at 01:16:34PM -0400, Jeff Dike wrote:
> da-x@gmx.net said:
> > My solution is: 
> > 
> >  * Let not build and run those utils on the build host, obviously.
> >  * All the required versions of the generated code for each of the
> >    targets will already reside in the tree, the build process will
> >    automatically pick up the right version and symlink to it.
> >  * Create a completely standalone program that embeds those utils 
> >    and generates the code. People who port UML to other 
> >    architectures will take this program, compile and run it on
> >    the target and put its output(s) in the tree.
> 
> I was thinking something similar, but differing in the details.  I was thinking
> about shipping the generated code in the tree, but non-cross builds would
> ignore it and just regenerate it.  Now, I'm thinking it shouldn't be in the
> tree, and that cross builds should put it there.
>
> 
> The other difference is that you're proposing a small build process to run
> on the target to generate the code.  I'm thinking that they should just copy
> the entire kernel tree over, and 'make arch_headers ARCH=um' or something.
> Then they would copy the directory containing the generated code back to the
> build host.
> 

Okay, so you say that a cross build procedure would need a one-time stage
where the person would generate the arch_headers at the host and then manually
copy the generated outputs back to the build host? Sounds difficult, but
people who are attempting cross builds are probably smart enough to understand
this, so it's good.

What sorts of changes are needed to be made in the build system to make 
it possible? I thought of adding $(CROSS_COMPILE) as a prefix to the filenames
of the generated outputs plus rules to generate symlinks that point from 
the normal filenames, in the case where $(CROSS_COMPILE) is activated.

Then, make arch_headers ARCH=um at the target will skip everything but 
running the helpers, packing their outputs to a .tar.gz, and something
like make install_arch_headers ARCH=um CROSS_COMPILE=[..] at the host 
will install those at the right spots in the tree with the given prefix
in CROSS_COMPILE.

Works for you?

-- 
Dan Aloni
da-x@gmx.net


-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise 
Linux in the Boardroom; in the Front Office; & in the Server Room 
http://www.enterpriselinuxforum.com
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  reply	other threads:[~2003-10-19 21:12 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-18 18:31 [uml-devel] Problem with UML cross compilation Dan Aloni
2003-10-19 17:16 ` Jeff Dike
2003-10-19 20:28   ` Dan Aloni [this message]
2003-10-25  1:34     ` Jeff Dike

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=20031019202825.GA10810@callisto.yi.org \
    --to=da-x@gmx.net \
    --cc=jdike@addtoit.com \
    --cc=user-mode-linux-devel@lists.sourceforge.net \
    /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