linux-um archives
 help / color / mirror / Atom feed
From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] UML on Alpha
Date: Tue, 23 Dec 2003 20:55:21 +0100	[thread overview]
Message-ID: <200312232055.21950.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <20031222041951.GB1023@erdos.home>

Alle 05:19, lunedì 22 dicembre 2003, Cameron Patrick ha scritto:

> Okay.  It doesn't seem to be there in 2.4.x, but I'll have a look at 2.6
> some time and see if that makes this problem disappear.
>
> | > cross-compile UML.  Unfortunately that would mean some way of getting
> | > rid of mk_sc/mk_thread/mk_kern/etc, and I'm not sure what the best
> | > approach to doing that would be :-/
> |
> | There was a bit of work in that direction a while back.  What I think
> | would be a good way to go is to have a arch_headers rule in the Makefile,
> | which would execute on the target, and generate the headers.  They would
> | land in a single directory, which you would then copy over to the build
> | box. The build there would use those headers, or generate them itself if
> | they weren't present.

Sorry, I'm giving a look here and it seems that the problem is just for 
mk_ptregs and mk_sc(since the others include the building kernel includes) 
and that they need only the target headers; this could maybe be accomplished 
just by copying them; and since what we *actually* need seems to be just asm/ 
headers, this can be accomplished simply by having a kernel tree with the asm 
symlink going to asm-<target arch>(that is much more available than the 
target machine itself, right?). So, specifying an include path for those 
files could be just fine, couldn't it? However, if we use your separate rule 
idea, within that we could use either just the headers or the host machine; 
so some problems go away(i.e. the kernel tree must match the target machine's 
one for the interested decls).

Note: mk_sc includes <signal.h>, which could be a problem. But it seems also 
that we can get away by just including asm/sigcontext.h.

Bye
-- 
cat <<EOSIGN
Paolo Giarrusso, aka Blaisorblade
Linux Kernel 2.4.21/2.6.0-test on an i686; Linux registered user n. 292729
EOSIGN



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id\x1278&alloc_id371&opÌk
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel

  parent reply	other threads:[~2003-12-23 19:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20  5:20 [uml-devel] UML on Alpha Cameron Patrick
2003-12-20 17:32 ` Jeff Dike
2003-12-22  4:19   ` Cameron Patrick
2003-12-23  1:10     ` Jeff Dike
2003-12-23 19:55     ` BlaisorBlade [this message]
2003-12-21 15:44 ` BlaisorBlade
2003-12-22  4:15   ` Cameron Patrick
2003-12-22  4:29     ` Matt Zimmerman
2003-12-24 12:46       ` BlaisorBlade

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=200312232055.21950.blaisorblade_spam@yahoo.it \
    --to=blaisorblade_spam@yahoo.it \
    --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