Note: I'm not subscribed, please Cc: [email protected]
I'm trying to compile 2.4.7 with resiser support and I get this:
make[3]: Entering directory `/usr/src/linux/fs/reiserfs'
gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
-Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
-pipe -mpreferred-stack-boundary=2 -march=i686 -c -o inode.o inode.c
inode.c: In function `reiserfs_get_block':
inode.c:803: warning: implicit declaration of function
`journal_transactioo_should_end'
inode.c:812: `retvcl' undeclared (first use in this function)
inode.c:812: (Each undeclared identifier is reported only once
inode.c:812: for each function it appears in.)
inode.c:812: parse error before `)'
inode.c: In function `init_inode':
inode.c:870: warning: implicit declaration of function `INIT_NIST_HEAD'
inode.c:876: warning: implicit declaration of function
`knode_items_version'
inode.c:876: invalid lvalue in assignment
inode.c:878: parse error before `>'
inode.c:882: structure has no member named `sd_atkme'
inode.c:889: `inofe' undeclared (first use in this function)
make[3]: *** [inode.o] Error 1
make[3]: Leaving directory `/usr/src/linux/fs/reiserfs'
make[2]: *** [first_rule] Error 2
make[2]: Leaving directory `/usr/src/linux/fs/reiserfs'
make[1]: *** [_subdir_reiserfs] Error 2
make[1]: Leaving directory `/usr/src/linux/fs'
make: *** [_dir_fs] Error 2
I'm using the same .config as I was in 2.4.4. I haven't had the time to
compare the two files to see what is different. If I don't get a solution
in the next day or so I will.
------------------------------------------------------------------------
| Mark Bishop ([email protected]) | Computer Engineer |
| 813.258.2390 | Network Engineer |
| http://bish.net | Embedded Programmer |
>
> Note: I'm not subscribed, please Cc: [email protected]
>
> I'm trying to compile 2.4.7 with resiser support and I get this:
>
> make[3]: Entering directory `/usr/src/linux/fs/reiserfs'
> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
> -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o inode.o inode.c
> inode.c: In function `reiserfs_get_block':
> inode.c:803: warning: implicit declaration of function
> `journal_transactioo_should_end'
> inode.c:812: `retvcl' undeclared (first use in this function)
Check your hardware. In my tree it is 'retval' as it should.
'a' and 'c' differ by a single bit ...
> inode.c:812: (Each undeclared identifier is reported only once
> inode.c:812: for each function it appears in.)
> inode.c:812: parse error before `)'
> inode.c: In function `init_inode':
> inode.c:870: warning: implicit declaration of function `INIT_NIST_HEAD'
As above. INIT_LIST_HEAD
> inode.c:876: warning: implicit declaration of function
> `knode_items_version'
As above. inode_items_version
> inode.c:876: invalid lvalue in assignment
> inode.c:878: parse error before `>'
Guessing: "->" <-----> "/>" ?
> inode.c:882: structure has no member named `sd_atkme'
As above. sd_atime
> inode.c:889: `inofe' undeclared (first use in this function)
As above. inode
You probably have a memory chip with broken bit 1 on some address(es)
Andrzej
In article <[email protected]>,
Andrzej Krzysztofowicz <[email protected]> writes:
>>
>> Note: I'm not subscribed, please Cc: [email protected]
>>
>> I'm trying to compile 2.4.7 with resiser support and I get this:
>>
>> make[3]: Entering directory `/usr/src/linux/fs/reiserfs'
>> gcc -D__KERNEL__ -I/usr/src/linux/include -Wall -Wstrict-prototypes
>> -Wno-trigraphs -O2 -fomit-frame-pointer -fno-strict-aliasing -fno-common
>> -pipe -mpreferred-stack-boundary=2 -march=i686 -c -o inode.o inode.c
>> inode.c: In function `reiserfs_get_block':
>> inode.c:803: warning: implicit declaration of function
>> `journal_transactioo_should_end'
>> inode.c:812: `retvcl' undeclared (first use in this function)
AK>
AK> Check your hardware. In my tree it is 'retval' as it should.
AK> 'a' and 'c' differ by a single bit ...
AK>
Dodgy RAM. Had the same problem some time ago. The machine would run
memtest86 as long as you like, no problem. Compile a kernel and I'd
get these bit errors. Reboot, powercycle, look at the file -- no
problem, probably compile next time.
Replacing the RAM fixed the problem.