linux-um archives
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Rusty Russell <rusty@rustcorp.com.au>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	user-mode-linux-devel@lists.sourceforge.net,
	Richard Weinberger <richard@nod.at>,
	LKML <linux-kernel@vger.kernel.org>,
	dhowells@redhat.com, Randy Dunlap <rdunlap@xenotime.net>,
	linux-next@vger.kernel.org
Subject: Re: [uml-devel] linux-next: Tree for July 26 (uml)
Date: Tue, 14 Aug 2012 15:26:53 +0100	[thread overview]
Message-ID: <15532.1344954413@warthog.procyon.org.uk> (raw)
In-Reply-To: <87a9xys53h.fsf@rustcorp.com.au>


Rusty Russell <rusty@rustcorp.com.au> wrote:

> > >   CC      arch/x86/um/../kernel/module.o
> > > arch/x86/um/../kernel/module.c:96:5: error: redefinition of 'apply_relocate_add'
> > > include/linux/moduleloader.h:64:19: note: previous definition of 'apply_relocate_add' was here
> > > make[2]: *** [arch/x86/um/../kernel/module.o] Error 1

Hmmm...  I'm not sure how to deal with this.  The problem is that UML doesn't
draw the:

	select MODULES_USE_ELF_REL if X86_32
	select MODULES_USE_ELF_RELA if X86_64

definitions from arch/foo/Kconfig that tell it what modules will look like.

Should I just enable both REL and RELA in UML, or is there a better way to do
this?

David

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
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:[~2012-08-14 14:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20120726150419.0de645e8750e3a15fa0f1aaa@canb.auug.org.au>
2012-07-26 15:18 ` linux-next: Tree for July 26 (uml) Randy Dunlap
2012-08-13 17:00   ` Randy Dunlap
2012-08-14  0:13     ` Rusty Russell
2012-08-14 14:26       ` David Howells [this message]
2012-08-14 14:31         ` [uml-devel] " Richard Weinberger
2012-08-14 14:51           ` David Howells
2012-08-14 14:54             ` David Howells
2012-08-14 14:57               ` Richard Weinberger
2012-08-14 15:06                 ` David Howells
2012-08-14 15:08                   ` Richard Weinberger
2012-08-14 15:15                     ` David Howells
2012-08-14 15:17                       ` Richard Weinberger
2012-08-14 17:41                         ` Randy Dunlap
2012-08-20  2:51                           ` [uml-devel] " Rusty Russell
2012-08-21 17:43                             ` Randy Dunlap
2012-08-22  1:17                               ` Rusty Russell
2012-08-14 15:09                   ` [uml-devel] " David Howells
2012-08-14 14:54             ` Richard Weinberger

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=15532.1344954413@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=richard@nod.at \
    --cc=rusty@rustcorp.com.au \
    --cc=sfr@canb.auug.org.au \
    --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