Re: Compile probs with yesterday's auto-snapshot

[Alex Zarochentsev <zam@namesys.com>]

On Tue, Aug 10, 2004 at 02:19:54PM -0500, David Dabbs wrote:
> 
> 
> Yesterday I kept having problems with an "incomplete type error" compiling
> yesterday's auto-snapshot. I finally ended up changing the
> CONFIG_REISER4_SYSFS define in fs/reiser4/kattr.h (I think that's the file)
> from (1) to (0). 

yes. everything fine in the BK, but latest autosnapshots were made from wrong
linux core patches.  I have re-done the autosnapshot script setup and will check
the next snapshot.

> 
> In a separate but related question, does the reiser4 patchset add the
> kernel-build configurable options to the kconfig e.g.
> REISER4_STATS/DEBUG/SYSFS/NOOPT/COPY_ON_CAPTURE/SYSCALL/<others?>...? I'm
> sure LARGE_KEY is there, but I can't remember which other one I saw. If it
> doesn't already should LARGE_KEY prompt with a default value of "Y"?
> 
> Also the READ.ME for the prior SNAPSHOT (03/26, yes ages ago I know) had the
> following notes. Since the recent 08/04 snapshot only notes that "This is
> mostly bug fix snapshot" should we assume that the prior notes are resolved
> or that there are still issues with the items? I've made some notes below
> 
> 
> 
> 1. Only i386 and UML on i386 are supported.
> ddabbs: Big endian appears to be supported.
> 
> 2. CONFIG_REISER4_FS_SYSCALL doesn't work.
> 
> 3. CONFIG_REISER4_NOOPT doesn't work.
> 
> 4. reiser4 has been tested as a root file system and works in read-only
>    mode, but:
> 
>        . remount is not yet supported, 
>        . support in boot-loaders may be missing
> 
> ddabbs: A grub patch is provided, so that comment is likely out-of-date.
> 
> 9. reiser4 can now be compiled as a module.
> 
> ddabbs: I don't think this is working yet.

hmm. I thought we made all needed symbols exportable. what is the problem?
> 
> c. CONFIG_REISER4_COPY_ON_CAPTURE is stabler than before.
> 
> d. readdir() over NFS has known problems.
> 
> e. mmap(2)-intensive workloads (iozone benchmark in particular) have
> problems in low-memory setups.
> 
> 
> David
> 
> 

-- 
Alex.