linux-um archives
 help / color / mirror / Atom feed
From: Martin Honermeyer <lists@strahlungsfrei.de>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] Re: [PATCH] UML/x86_64
Date: Thu, 17 Jun 2004 20:53:23 +0200	[thread overview]
Message-ID: <caq56s$5vg$1@sea.gmane.org> (raw)
In-Reply-To: 20040501170905.GA7655@ccure.user-mode-linux.org

Hi Jeff,

thanks for your work! I just tried the patch on my AMD64 machine. "make
linux ARCH=um" fails with

  CC      arch/um/kernel/ksyms.o
arch/um/kernel/ksyms.c:91: error: `dump_thread' undeclared here (not in a
function)
arch/um/kernel/ksyms.c:91: error: initializer element is not constant
arch/um/kernel/ksyms.c:91: error: (near initialization for
`__ksymtab_dump_thread.value')
arch/um/kernel/ksyms.c:91: error: __ksymtab_dump_thread causes a section
type conflict
make[1]: *** [arch/um/kernel/ksyms.o] Error 1


When commenting out that line in arch/um/kernel/ksyms.c and disabling module
support in the kernel configuration, it works! So, just a little correction
to your patch. Now I'll try and see if it works ;)


Greetings,
Martin


Jeff Dike wrote:

> UML has been ported to x86_64.  The patch for 2.6.4 is available at
> http://www.user-mode-linux.org/mirror/uml-patch-x86-64-2.6.4.bz2
> 
> Note that this is separate from the 2.6.4 UML patch, and must be
> applied to a 2.6.4 + uml-patch-2.6.4 tree.  It will remain separate
> until I get it all merged cleanly into my tree.  At that point, the
> separate x86_64 patch will disappear.
> 
> This patch is fairly nasty in places, and the build is also fairly
> unclean, so avert your eyes if you are squeamish.  This will get
> better as I merge it into my pool.
> 
> The nastiness aside, it does build and you do get a robust UML.
> 
> My thanks go to PathScale (pathscale.com) for sponsoring this work and
> providing access to hardware to make it possible.
> 
> Finally, as I do the merge (and afterwards), I need access to an
> Opteron to make sure I don't break this port.  So, if anyone has such
> a box that I can have access to, let me know.
> 
> Jeff





-------------------------------------------------------
This SF.Net email is sponsored by The 2004 JavaOne(SM) Conference
Learn from the experts at JavaOne(SM), Sun's Worldwide Java Developer
Conference, June 28 - July 1 at the Moscone Center in San Francisco, CA
REGISTER AND SAVE! http://java.sun.com/javaone/sf Priority Code NWMGYKND
_______________________________________________
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:[~2004-06-17 20:00 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20040501170905.GA7655@ccure.user-mode-linux.org>]

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='caq56s$5vg$1@sea.gmane.org' \
    --to=lists@strahlungsfrei.de \
    --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