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

[-- Attachment #1: Type: text/plain, Size: 881 bytes --]

Am 14.08.2012 16:26, schrieb David Howells:
> 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?

Is there no way to get this information from the UML subarch?
Which is currently X86_32 or X86_64.

Thanks,
//richard


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  reply	other threads:[~2012-08-14 14:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26  5:04 linux-next: Tree for July 26 Stephen Rothwell
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
2012-08-14 14:31         ` Richard Weinberger [this message]
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                           ` Rusty Russell
2012-08-21 17:43                             ` Randy Dunlap
2012-08-22  1:17                               ` Rusty Russell
2012-08-14 15:09                   ` David Howells
2012-08-14 14:54             ` Richard Weinberger
2012-07-26 15:43 ` linux-next: Tree for July 26 (vfio) Randy Dunlap
2012-07-26 16:16   ` Alex Williamson

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=502A613F.1090600@nod.at \
    --to=richard@nod$(echo .)at \
    --cc=dhowells@redhat$(echo .)com \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=rdunlap@xenotime$(echo .)net \
    --cc=rusty@rustcorp$(echo .)com.au \
    --cc=sfr@canb$(echo .)auug.org.au \
    --cc=user-mode-linux-devel@lists$(echo .)sourceforge.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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