From: Jonathan Hudson <jonathan@daria.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel version 2.4.7 compile errors
Date: Mon, 30 Jul 2001 09:34:36 GMT [thread overview]
Message-ID: <35a9.3b652a2c.b5ca8@trespassersw.daria.co.uk> (raw)
In-Reply-To: <fa.iv417uv.92su9n@ifi.uio.no> <fa.dgc3h1v.19gsvaq@ifi.uio.no>
In article <fa.dgc3h1v.19gsvaq@ifi.uio.no>,
Andrzej Krzysztofowicz <kufel!ankry@green.mif.pg.gda.pl> writes:
>>
>> Note: I'm not subscribed, please Cc: mark@bish.net
>>
>> 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.
next parent reply other threads:[~2001-07-30 9:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.iv417uv.92su9n@ifi.uio.no>
[not found] ` <fa.dgc3h1v.19gsvaq@ifi.uio.no>
2001-07-30 9:34 ` Jonathan Hudson [this message]
2001-07-29 21:10 Mark
2001-07-29 22:07 ` Andrzej Krzysztofowicz
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=35a9.3b652a2c.b5ca8@trespassersw.daria.co.uk \
--to=jonathan@daria.co.uk \
--cc=linux-kernel@vger.kernel.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®