Not certain if it's an on on-disk structure - it is used all over,
but the comments in it would suggest that it is in-memory only
(especially since it contains at least one pointer, which would
make little sense in an on disk struct).
Even in that case, the purpose of the cassert() in the coords_
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Just checked - the Andrew Morton -mm4 patch has the offending cassert
> ifdef'd out.
>
> This is why the reiser4 stuff compiles on 64bit platforms in that patch.
Hummm, I wonder if that structure gets written out to disk?
If so, I'm thinking the th
EMAIL PROTECTED]; [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: RE: reiser4 kernel patch
It was actually a build problem - a cassert() in coord.c triggers an odd
switch statement error (by design).
Essentially the author is trying to make certain that no new members were
added to the coord_t
kernel sources.
...tom
-Original Message-
From: Tyson Whitehead [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 09, 2004 3:13 PM
To: [EMAIL PROTECTED]
Cc: Thomas Evans; [EMAIL PROTECTED]
Subject: Re: reiser4 kernel patch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I was tryi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> I was trying out the reiser4 kernel patch and ran in a build-time assert on
> my Alpha machine.
I compiled stock 2.6.8.1 with the mm4 (Andrew Morton -- includes Reiser 4)
patch set. Didn't have any compile time problems. Don't
Hi all -
I was trying out the reiser4 kernel patch and ran in a build-time assert on
my Alpha machine.
I wasn't sure what package I should attribute the issue to - any suggestions
would be great!
Thanks,
...tom
6 matches
Mail list logo
