From: Ming-Wei Shih <xming@spaceball.cjb.net>
To: xen-devel@lists.sourceforge.net
Subject: Re: Xen and reiser4
Date: Wed, 15 Dec 2004 19:56:50 +0100 [thread overview]
Message-ID: <41C088F2.4070400@spaceball.cjb.net> (raw)
In-Reply-To: <41C08801.4060908@spaceball.cjb.net>
>>> Hi all
>>>
>>> Thanks to Milan I am able to get further with xen and reiser4
>>>
>>> - In swap line 6 and 7 status_flags.c
>>>
>>> #include <linux/bio.h>
>>> #include <linux/page-flags.h>
>>>
>>>
>>> - PACKED is redefined, but the definitions are the same, so the gcc
>>> warning can be ignored IMO
>>>
>>> dformat.h:#define PACKED __attribute__((packed))
>>> xen.h:#define PACKED __attribute__ ((packed))
>>
>>
>>
>
> Yup, these 2 are the same, I just didn't recall whether they were
> exactly the same. And I renamed reiser4's definition (and its usage
> inside reiser4) because the messages caused by it somehow prevented me
> from seeing the actual error :)
>
>>>
>>> however during linking I get this, and I could'nt find
>>> perthread_pages_count anywher in the kernel
>>> src tree
>>>
>>> LD init/built-in.o
>>> LD .tmp_vmlinux1
>>> fs/built-in.o(.text+0x37701): In function `carry':
>>> : undefined reference to `perthread_pages_count'
>>> fs/built-in.o(.text+0x3771e): In function `carry':
>>> : undefined reference to `perthread_pages_reserve'
>>> fs/built-in.o(.text+0x37821): In function `carry':
>>> : undefined reference to `perthread_pages_count'
>>> fs/built-in.o(.text+0x3782f): In function `carry':
>>> : undefined reference to `perthread_pages_release'
>>> make: *** [.tmp_vmlinux1] Error 1
>>
>>
>>
>
> Now this is strange. In my sources with xen+reiser4, I get these three
> occurences which are defining this symbol:
>
> | ./include/linux/gfp.h:int perthread_pages_count(void);
> | ./mm/page_alloc.c:int perthread_pages_count(void)
> | ./mm/page_alloc.c:EXPORT_SYMBOL(perthread_pages_count);
>
> (where the first is defining the function for use in other files, the
> second will be followed by the actual code of the function, and the
> third exports the function as a symbol which is callable by other
> modules)
>
> I don't think xen doesn't use page_alloc.c (in addition, it got built in
> my xen tree), so maybe you want to try a "make mrproper"? (put backup
> your .config before this, or do a "make clean"...)
No matter what I do (mrproper, different reiser4 patches, untar from
clean src+patch) I always
get this error on 2 machines, clean 2.6.9 without patches builts
correctly. Any clues?
TIA
Ming-Wei
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next parent reply other threads:[~2004-12-15 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <41C08801.4060908@spaceball.cjb.net>
2004-12-15 18:56 ` Ming-Wei Shih [this message]
2004-12-17 19:17 ` Re: Xen and reiser4 Ming-Wei Shih
2005-01-11 20:12 ` Ming-Wei Shih
2005-01-11 21:23 ` Jan Kundrát
2005-01-11 23:37 ` Ming-Wei Shih
2005-01-12 14:26 ` Jan Kundrát
2005-01-12 19:00 ` Ming-Wei Shih
2005-01-12 20:09 ` Jerome Brown
2005-01-12 21:14 ` nfsroot and brige Adam Sulmicki
2005-01-12 21:44 ` double free Adam Sulmicki
2005-01-12 22:04 ` Keir Fraser
2005-01-12 22:32 ` Adam Sulmicki
2005-01-12 22:31 ` Keir Fraser
2005-01-12 22:57 ` Adam Sulmicki
2005-01-17 7:56 ` nfsroot and brige Adam Sulmicki
2005-01-12 22:00 ` Re: Xen and reiser4 Jan Kundrát
2005-01-12 23:09 ` Jerome Brown
2005-01-13 13:43 ` Jan Kundrát
2005-01-17 15:22 ` Jan Kundrát
2005-01-11 22:28 ` Mark A. Williamson
2005-01-12 8:09 ` Ming-Wei Shih
2005-01-12 14:16 ` Jan Kundrát
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=41C088F2.4070400@spaceball.cjb.net \
--to=xming@spaceball.cjb.net \
--cc=xen-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.