From: Blaisorblade <blaisorblade@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Raphael Bossek <raphael.bossek@gmx.de>
Subject: Re: [uml-devel] Linking .tmp_vmlinuux1 fails with 2.6.12-mm1
Date: Fri, 24 Jun 2005 12:55:45 +0200 [thread overview]
Message-ID: <200506241255.46532.blaisorblade@yahoo.it> (raw)
In-Reply-To: <42BBA6F1.9080704@gmx.de>
On Friday 24 June 2005 08:23, Raphael Bossek wrote:
> Hi,
>
> after applying the TT_MODE build patch I run into the following problem
> with linux 2.6.12-mm1:
Does that happen with 2.6.12-current? Here it seems it doesn't; so I'll have
to look into -mm only; otherwise I'll look at gcc-2.95 differences.
> gcc-2.95 -Wp,-MD,init/.version.o.d -nostdinc -isystem
> /usr/lib/gcc-lib/i386-linux/2.95.4/include -D__KERNEL__ -Iinclude -Wall
> -Wstri
> ld -r -o init/built-in.o init/main.o init/version.o init/mounts.o
> init/initramfs.o init/calibrate.o
> gcc-2.95 -static -Wl,--wrap,malloc -Wl,--wrap,free
> -Wl,--wrap,calloc -o .tmp_vmlinux1 -Wl,-T,arch/um/kernel/vmlinux.lds
> init/b
> arch/um/sys-i386/built-in.o(*ABS*+0x73c706fe): In function `__crc_kunmap':
> module.c: multiple definition of `__crc_kunmap'
> arch/um/sys-i386/built-in.o(*ABS*+0xe7c48b45): In function
> `__crc_kmap_atomic':
> module.c: multiple definition of `__crc_kmap_atomic'
> arch/um/sys-i386/built-in.o(*ABS*+0x1889f5f3): In function
> `__crc_kmap_atomic_to_page':
> module.c: multiple definition of `__crc_kmap_atomic_to_page'
> arch/um/sys-i386/built-in.o(*ABS*+0xd837acb7): In function `__crc_kmap':
> module.c: multiple definition of `__crc_kmap'
> collect2: ld returned 1 exit status
>
> --
> Raphael Bossek
--
Inform me of my mistakes, so I can keep imitating Homer Simpson's "Doh!".
Paolo Giarrusso, aka Blaisorblade (Skype ID "PaoloGiarrusso", ICQ 215621894)
http://www.user-mode-linux.org/~blaisorblade
___________________________________
Yahoo! Mail: gratis 1GB per i messaggi e allegati da 10MB
http://mail.yahoo.it
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&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-06-24 10:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-24 6:23 [uml-devel] Linking .tmp_vmlinuux1 fails with 2.6.12-mm1 Raphael Bossek
2005-06-24 10:55 ` Blaisorblade [this message]
2005-06-24 13:43 ` Jeff Dike
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=200506241255.46532.blaisorblade@yahoo.it \
--to=blaisorblade@yahoo.it \
--cc=raphael.bossek@gmx.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