From: "gboutwel" <gboutwel@praize.com>
To: user-mode-linux-devel@lists.sourceforge.net
Subject: [uml-devel] uml-2.6.8-rc2 (2.6.8-rc2 w/ uml-patch-2.6.7-01)
Date: 23 Jul 2004 21:43:12 -0000 [thread overview]
Message-ID: <20040723214312.14567.qmail@praize.com> (raw)
I'm testing the 2.6.8 waters. Looks like it's not been included
in the rc2 version yet. It's in the mm1 version though... so
there's hope. Here's what I've done:
1) tar jzf linux-2.6.7.tar.bz2
2) mv linux-2.6.7 linux-2.6.8-rc2-1um
3) bzcat patch-2.6.8-rc2.bz2 | patch -p1
4) bzcat uml-patch-2.6.7-01.bz2 | patch -p1 --dry-run | less
* not bad, just shows 1 reject, which is the removal of an
#include from init_setup.c
5) cp ~/2.6.7/config-2.6.7-1um .config
6) make oldconfig ARCH=um
7) make linux ARCH=um
* this fails on arch/um/drivers/stdio_console.c with:
arch/um/drivers/stdio_console.c:207: error: conflicting types
for `console_device'
include/linux/console.h:107: error: previous declaration of `console_device'
Where:
include/linux/console.h:107 extern struct tty_driver *console_device(int
*);
arch/um/drivers/stdio_console.c:207 has struct tty_driver *console_device(struct
console *c, int *index)
so, on a wild 'whim' I changed console_device in stdio_console.c
to uml_console_device.
That compiles, but then it ends with an linker error:
vmlinux(.text+0x2d8b0): In function `alloc_pidmap':
: undefined reference to `find_next_zero_bit'
vmlinux(.text+0x4faef): In function `get_unused_fd':
: undefined reference to `find_next_zero_bit'
vmlinux(.text+0x5fcd8): In function `locate_fd':
: undefined reference to `find_next_zero_bit'
vmlinux(.text+0x7e3f1): In function `scan_bitmap_block':
: undefined reference to `find_next_zero_bit'
vmlinux(.text+0x9f49e): In function `reiserfs_in_journal':
: undefined reference to `find_next_zero_bit'
vmlinux(.text+0xa6bd0): more undefined references to `find_next_zero_bit'
follow
vmlinux(.text+0xb7905): In function `sub_alloc':
: undefined reference to `find_next_bit'
vmlinux(.init.text+0x43d0): In function `__alloc_bootmem_core':
: undefined reference to `find_next_zero_bit'
collect2: ld returned 1 exit status
make: *** [linux] Error 1
Probably something simple, but I wanted to discuss with folks
more in the now on if the above (stdio_console) fix was the right
one, and to find out if anyone else has an idea of how to fixe
the find_next_zero_bit error.
Thanks,
George
----------------------------------------------------
Need to store your files online?
Upload them for free in Praize Briefcase
http://www.praize.com/cgi-bin/members/mybriefcase.cgi
-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&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 reply other threads:[~2004-07-23 21:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-23 21:43 gboutwel [this message]
2004-07-24 3:38 ` [uml-devel] uml-2.6.8-rc2 (2.6.8-rc2 w/ uml-patch-2.6.7-01) David T Hollis
2004-07-26 15:05 ` BlaisorBlade
-- strict thread matches above, loose matches on Subject: below --
2004-07-27 22:08 gboutwel
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=20040723214312.14567.qmail@praize.com \
--to=gboutwel@praize.com \
--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