[haiku-development] break build on Dano

hello all,

    
Since the last break, the changes by axel have improved the thing, but I get 
still finalizing the image !!

see below:

C++ generated/objects/dano/x86/release/tools/fs_shell/atomic.o
/boot/develop/headers/be/support/SupportDefs.h: In method `status_t 
lock_status_t::status() const':
In file included from /boot/home/Divers/haiku/headers/build/
HaikuBuildCompatibility.h:23,
                 from /boot/home/Divers/haiku/src/tools/fs_shell/
compatibility.h:10,
                 from /boot/home/Divers/haiku/src/tools/fs_shell/
atomic.cpp:6:
/boot/develop/headers/be/support/SupportDefs.h:30: `B_OK' undeclared (first 
use this function)
/boot/develop/headers/be/support/SupportDefs.h:30: (Each undeclared 
identifier is reported only once
/boot/develop/headers/be/support/SupportDefs.h:30: for each function it 
appears in.)
/boot/develop/headers/be/support/SupportDefs.h:30: warning: control reaches 
end of non-void function `lock_status_t::status() const'

gcc -c "src/tools/fs_shell/atomic.cpp" -O2 -Wall -Wno-trigraphs -Wno-ctor-
dtor-privacy -Woverloaded-virtual -Wpointer-arith -Wcast-align -Wsign-compare 
-Wno-multichar -DFS_SHELL=1 -D_ZETA_USING_DEPRECATED_API_=1 -
D_ZETA_TS_FIND_DIR_=1 -DARCH_x86 -D_NO_INLINE_ASM -DCOMPILE_FOR_R5 -
DHAIKU_HOST_PLATFORM_DANO -Isrc/tools/fs_shell -Igenerated/objects/common/
tools/fs_shell -Igenerated/objects/dano/x86/common/tools/fs_shell -Igenerated
/objects/haiku/x86/common/tools/fs_shell -I- -Iheaders/build -Iheaders/
private/fs_shell -Iheaders/private/shared -Iheaders/build/host/dano -Iheaders
/build/host/beos_common -o "generated/objects/dano/x86/release/tools/fs_shell
/atomic.o" ;

...failed C++ generated/objects/dano/x86/release/tools/fs_shell/atomic.o ...
...skipped <build>fs_shell.a for lack of <src!tools!fs_shell>atomic.o...
...skipped <build>bfs_shell for lack of <build>fs_shell.a...
...skipped <HaikuImage>haiku.image-init-vars for lack of <build>bfs_shell...
...skipped haiku.image for lack of <HaikuImage>haiku.image-init-vars...
...failed updating 1 target(s)...
...skipped 4 target(s)...
...updated 1 target(s)...      

        
If someone has an idea?

regards.

Raynald.

Other related posts: