Can't build ramfs

[humdinger]

This is hrev47613.

Jamming ramfs fails:

/HiQ-Data/sources/haiku> jam -q ramfs
Starting build of type regular ... 
WebKit build feature not available for x86_gcc2 
Gutenprint support not available on x86 
qrencode support not available on x86 
...patience...
...found 5249 target(s)...
...updating 17 target(s)...
C++ generated/objects/haiku/x86_gcc2/release/add-ons/kernel/file_systems/ramfs/Attribute.o 
In file included from /HiQ-Data/sources/haiku/headers/private/kernel/lock.h:15,
                 from /HiQ-Data/sources/haiku/headers/private/userlandfs/shared/RecursiveLock.h:8,
                 from /HiQ-Data/sources/haiku/headers/private/userlandfs/shared/Locker.h:12,
                 from /HiQ-Data/sources/haiku/src/add-ons/kernel/file_systems/ramfs/Volume.h:32,
                 from /HiQ-Data/sources/haiku/src/add-ons/kernel/file_systems/ramfs/Attribute.cpp:8:
/HiQ-Data/sources/haiku/headers/private/kernel/arch/atomic.h:13: arch_atomic.h: No such file or directory

waddlesplash suggests ramfs wasn't adapted to the new scheduler(?).
Complete output attached.

[humdinger]

building ramfs failed

[bonefish]

Unfortunately it hasn't been adjusted to quite a few things -- kallisti worked on it last, but I don't know what state it is in, now. While it would be pretty nice to have, making it work properly (file cache support, avoiding use of virtual memory) would be quite a bit of work.

[pulkomandy]

ramfs has been fixed in hrev53437. A nice thing to mention in our beta2 release notes, I guess?

[waddlesplash]

Well, RAMFS still has some outstanding bugs that prevent its use, so maybe not.