From: Gerd Knorr <kraxel@bytesex.org>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: Supporting building on x86-64 host as 32-bit UML
Date: Sun, 20 Mar 2005 16:03:06 +0100 [thread overview]
Message-ID: <20050320150306.GA14594@bytesex> (raw)
In-Reply-To: <200503191904.05870.blaisorblade@yahoo.it>
> 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 ;)
> 2) using the proper options for the tools (addressed partially by the
> patch below)
Probably still needed. Maybe not any more with gcc4, I remember there
was some discussion among the gcc folks to make gcc default to -m64 /
-m32 depending on the current personalily. In that case the linux32
thingy mentioned above should catch that one as well. Not sure that
actually happened.
> 3) using the proper headers (asm-i386 instead of asm-x86_64)... Fedora
linux32 should fix that one as well.
> +AFLAGS += -m32
> +CFLAGS += -m32
I think that can also be fixed on the make command line, with a small
wrapper script -- named make32 for example -- doing something like this:
#!/bin/sh
exec linux32 make CC="gcc -m32" AS="as -m32" ... "$@"
Last time I tried I ran into the problem that the glibc headers of the
x86_64 biarch compiler slightly different from the ones on a real i386
machine, thus some #ifdefs in uml userspace code didn't work as expected
and broke the build.
> +HOSTCFLAGS += -m32
> +HOSTLDFLAGS += -m32
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.
Gerd
--
#define printk(args...) fprintf(stderr, ## args)
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&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
next prev parent reply other threads:[~2005-03-20 14:08 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 ` Gerd Knorr [this message]
2005-03-22 17:53 ` [uml-devel] " Blaisorblade
2005-03-22 19:07 ` Gerd Knorr
2005-03-22 20:02 ` 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=20050320150306.GA14594@bytesex \
--to=kraxel@bytesex.org \
--cc=blaisorblade@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