All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Landley <rob@landley.net>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] What's different about building for x86-64?
Date: Fri, 4 Nov 2005 08:07:03 -0600	[thread overview]
Message-ID: <200511040807.03708.rob@landley.net> (raw)

Daving Lang grabbed my firmware-linux build script and tried to build it on 
x86-64, and it barfed trying to compile User Mode Linux:

gcc -Wall -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing 
-fno-common -ffreestanding -O2 -fomit-frame-pointer -D__arch_um__ 
-DSUBARCH=\"x86_64\" -Dvmap=kernel_vmap -Iarch/um/include 
-I/root/firmware-build-0.8.9/tmpdir/linux-2.6.13.2/arch/um/kernel/tt/include 
-I/root/firmware-build-0.8.9/tmpdir/linux-2.6.13.2/arch/um/kernel/skas/include 
-fno-builtin -D_GNU_SOURCE -D_LARGEFILE64_SOURCE -S -o 
arch/um/user-offsets.s arch/um/sys-x86_64/user-offsets.c
arch/um/sys-x86_64/user-offsets.c: In function `foo':
arch/um/sys-x86_64/user-offsets.c:24: error: structure has no member named 
`rbx'
arch/um/sys-x86_64/user-offsets.c:25: error: structure has no member named 
`rcx'
...
and so on.

My build is basically extracting the 2.6.14 tarball, adding the squashfs 
patch, and then doing this:

make ARCH=um O=../linux-build allnoconfig &&
cd ../linux-build &&
cat >> .config << EOF &&
CONFIG_MODE_SKAS=y
CONFIG_BINFMT_ELF=y
CONFIG_HOSTFS=y
CONFIG_SYSCTL=y
CONFIG_STDERR_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_UBD=y
CONFIG_TMPFS=y
CONFIG_SWAP=y
CONFIG_LBD=y
CONFIG_EXT2_FS=y
CONFIG_PROC_FS=y
CONFIG_SQUASHFS=y
CONFIG_SQUASHFS_FRAGMENT_CACHE_SIZE=3
CONFIG_ZLIB_INFLATE=y
EOF
yes "" | make ARCH=um oldconfig &&
make ARCH=um &&

It's not working, and I don't have an x86-64 machine to test this on.  I can 
only assume the config file is wrong, but it's in a way that oldconfig isn't 
fixing...

I don't know quite how ARCH=um figures out whether it's derived from ARCH=i386 
or ARCH=x86-64...

Rob


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
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-11-04 14:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-04 14:07 Rob Landley [this message]
2005-11-04 16:04 ` [uml-devel] What's different about building for x86-64? Jeff Dike
2005-11-04 15:38   ` Rob Landley
2005-11-04 17:01     ` 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=200511040807.03708.rob@landley.net \
    --to=rob@landley.net \
    --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 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.