linux-um.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Blaisorblade <blaisorblade@yahoo.it>
To: Gerd Knorr <kraxel@bytesex.org>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: Supporting building on x86-64 host as 32-bit UML
Date: Tue, 22 Mar 2005 21:02:11 +0100	[thread overview]
Message-ID: <200503222102.11643.blaisorblade@yahoo.it> (raw)
In-Reply-To: <20050322190731.GA8975@bytesex>

On Tuesday 22 March 2005 20:07, Gerd Knorr wrote:
> On Tue, Mar 22, 2005 at 06:53:20PM +0100, Blaisorblade wrote:
> > On Sunday 20 March 2005 16:03, Gerd Knorr wrote:
> > > > 1) how the user must choose what he wants (SUBARCH=i386 can be
> > > > useful, maybe a Kconfig option would be nice - we need to choose the
> > > > default depending on the host arch).
> > >
> > > That one is easy -- just use "linux32 make ...".  That will switch the
> > > personality and "uname" will return "i686" instead of "x86_64" then ;)
> >
> > linux32 is a SuSE specific alias like the "i386" for Fedora, right (they
> > both alias setarch, IIRC)?
>
> Don't have a "setarch" binary here.  But most likely they do almost the
> same, yes.
>
> > > Not needed I think.  Thats used for kconfig and other stuff which runs
> > > on the _host_ machine (for cross compiles), thus it doesn't hurt if it
> > > is 64 bit.
> >
> > I'm not sure, but that's probably needed for the userspace utilities that
> > print out some headers (with offsets inside host proc. specific structs).
>
> Uhm, ok, then it probably is needed.  This also means that you can't
> cross-compile uml kernels, right?
Eh? Those utilities must run on the compile host, and they are compiled with 
HOSTCC, but use the targets header. So on x86-64 / x86 it works, but probably 
in general you are right (I don't have the whole picture right now, but this 
makes sense).

That said, Al Viro changed this significantly when working on making UML 
cross-compile well, so you again are probably right. I'm currently merging 
his work in little pieces.
-- 
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
http://www.user-mode-linux.org/~blaisorblade




-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
_______________________________________________
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:[~2005-03-22 20:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-19 18:04 [uml-devel] Supporting building on x86-64 host as 32-bit UML Blaisorblade
2005-03-20 15:03 ` [uml-devel] " Gerd Knorr
2005-03-22 17:53   ` Blaisorblade
2005-03-22 19:07     ` Gerd Knorr
2005-03-22 20:02       ` Blaisorblade [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=200503222102.11643.blaisorblade@yahoo.it \
    --to=blaisorblade@yahoo.it \
    --cc=kraxel@bytesex.org \
    --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;
as well as URLs for NNTP newsgroup(s).