From: Dave Kleikamp <shaggy@austin.ibm.com>
To: Perlbroker <minime@sdf.lonestar.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: PROBLEM: 2.6.7 does not compile (jfs errors)
Date: Wed, 16 Jun 2004 11:27:42 -0500 [thread overview]
Message-ID: <1087403262.29041.25.camel@shaggy.austin.ibm.com> (raw)
In-Reply-To: <20040616133944.GA1987@8128.biz>
On Wed, 2004-06-16 at 08:39, Perlbroker wrote:
> CC [M] fs/jfs/jfs_dtree.o
> fs/jfs/jfs_dtree.c: In function `add_index':
> fs/jfs/jfs_dtree.c:388: parse error before `struct'
> fs/jfs/jfs_dtree.c:389: `temp_table' undeclared (first use in this function)
> fs/jfs/jfs_dtree.c:389: (Each undeclared identifier is reported only once
> fs/jfs/jfs_dtree.c:389: for each function it appears in.)
> make[3]: *** [fs/jfs/jfs_dtree.o] Error 1
> make[2]: *** [fs/jfs] Error 2
> make[1]: *** [fs] Error 2
> make[1]: Leaving directory `/usr/src/linux-2.6.7'
This was reported in another thread by Tomas Szepe. I don't know why
this sometimes compiles cleanly, but this patch should fix it:
diff -urp linux-2.6.7/fs/jfs/jfs_dtree.c linux/fs/jfs/jfs_dtree.c
--- linux-2.6.7/fs/jfs/jfs_dtree.c 2004-06-16 07:38:20.244688936 -0500
+++ linux/fs/jfs/jfs_dtree.c 2004-06-16 07:46:38.210986552 -0500
@@ -374,6 +374,8 @@ static u32 add_index(tid_t tid, struct i
return index;
}
if (index == (MAX_INLINE_DIRTABLE_ENTRY + 1)) {
+ struct dir_table_slot temp_table[12];
+
/*
* It's time to move the inline table to an external
* page and begin to build the xtree
@@ -385,7 +387,6 @@ static u32 add_index(tid_t tid, struct i
* Save the table, we're going to overwrite it with the
* xtree root
*/
- struct dir_table_slot temp_table[12];
memcpy(temp_table, &jfs_ip->i_dirtable, sizeof(temp_table));
/*
--
David Kleikamp
IBM Linux Technology Center
next prev parent reply other threads:[~2004-06-16 16:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 13:39 Perlbroker
2004-06-16 16:27 ` Dave Kleikamp [this message]
2004-06-16 16:57 ` Geert Uytterhoeven
2004-06-16 22:48 ` Leon Woestenberg
2004-06-18 11:56 ` szonyi calin
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=1087403262.29041.25.camel@shaggy.austin.ibm.com \
--to=shaggy@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=minime@sdf.lonestar.org \
/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
all inboxes | Powered by JetHome®