From: "E.Gryaznova" <grev@namesys.com>
To: jimm@simutronics.com
Cc: reiserfs-list@namesys.com
Subject: Re: Compile error 2.6.9
Date: Tue, 02 Nov 2004 13:35:45 +0300 [thread overview]
Message-ID: <41876301.6030504@namesys.com> (raw)
In-Reply-To: <4186D662.7080407@namesys.com>
[-- Attachment #1: Type: text/plain, Size: 1615 bytes --]
E.Gryaznova wrote:
> Jim Miller wrote:
>
>> I got the follow errors while compiling 2.6.9 linux kernel. I followed
>> these dirs:
>> 1. get 2.6.9 (ftp.kernel.org:/pub/linux/kernel/v2.6/linux-2.6.9.tar.gz)
>> tar zxf linux-2.6.9.tar.gz -C /usr/src
>> 2. get reiser4 core patches:
>> ftp.namesys.com:/pub/reiser4-for-2.6.9/2.6.9.diff
>> cd /usr/src/linux-2.6.9
>> cat 2.6.9.diff | patch -p1
>> 3. add reiser4 to linux-2.6.9
>> ftp.namesys.com:/pub/reiser4-for-2.6.9/reiser4.tar.bz2
>> cd /usr/src/linux-2.6.9/fs
>> tar jxf reiser4.tar.bz2
>> 4. patch reiser4 to match 2.6.9
>> ftp.namesys.com:/pub/reiser4-for-2.6.9/reiser4-for-2.6.9.diff
>> cd /usr/src/linux-2.6.9
>> cat reiser4-for-2.6.9.diff | patch -p1
>>
>> All of the patches applied successfully. Any suggestions would be
>> appreciated.
>>
>> CC fs/reiser4/plugin/cryptcompress.o
>> fs/reiser4/plugin/cryptcompress.c: In function `inflate_cluster':
>> fs/reiser4/plugin/cryptcompress.c:1018: parse error before `*'
>> fs/reiser4/plugin/cryptcompress.c:1019: `cplug' undeclared (first use in
>> this function)
>> fs/reiser4/plugin/cryptcompress.c:1019: (Each undeclared identifier is
>> reported only once
>> fs/reiser4/plugin/cryptcompress.c:1019: for each function it appears
>> in.)
>> make[3]: *** [fs/reiser4/plugin/cryptcompress.o] Error 1
>> make[2]: *** [fs/reiser4] Error 2
>> make[1]: *** [fs] Error 2
>> make[1]: Leaving directory `/usr/src/linux-2.6.9'
>> make: *** [stamp-build] Error 2
>>
>>
>>
>>
>> Thanks,
>> Jim
>>
> Hello,
> would you please send me your config file?
>
> Thanks,
> Lena
Would you please try this patch?
Thanks,
Lena.
[-- Attachment #2: cryptcompress.c.diff --]
[-- Type: text/plain, Size: 499 bytes --]
===== plugin/cryptcompress.c 1.133 vs edited =====
--- 1.133/plugin/cryptcompress.c 2004-10-27 19:55:54 +04:00
+++ edited/plugin/cryptcompress.c 2004-11-02 12:12:18 +03:00
@@ -1013,9 +1013,10 @@
assert("edward-907", !tfm_cluster_is_uptodate(tc));
if (inode_get_crypto(inode) != NULL) {
+ crypto_plugin * cplug;
+
/* FIXME-EDWARD: isn't support yet */
assert("edward-908", 0);
- crypto_plugin * cplug;
cplug = inode_crypto_plugin(inode);
assert("edward-617", cplug != NULL);
prev parent reply other threads:[~2004-11-02 10:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-01 22:40 Compile error 2.6.9 Jim Miller
2004-11-02 0:35 ` E.Gryaznova
2004-11-02 10:35 ` E.Gryaznova [this message]
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=41876301.6030504@namesys.com \
--to=grev@namesys.com \
--cc=jimm@simutronics.com \
--cc=reiserfs-list@namesys.com \
/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.