[interfacekit] Re: Fun with the registrar

On Tuesday 05 November 2002 03:09 pm, you wrote:
> So, just for kicks and giggles, I decided to try and run all the unit
> tests today, just to see if they would all pass.  A few BAppFileInfo
> tests failed and, of course, the very first BApplication test failed
> because it couldn't find the OBOS registrar.  So I built the registrar

What's this about you being able to build the registrar?  It doesn't build for 
me using a fresh cvs tree (a bunch of other things fail too).  I did a full 
build and 427 targets failed, 121 were skipped, and 1233 were updated.  I get 
boatloads of header related errors like:

In file included from /boot/develop/headers/cpp/iostream.h:31,
                 from /boot/develop/headers/cpp/stl_algobase.h:53,
                 from /boot/develop/headers/cpp/vector:30,
                 from headers/private/app/LooperList.h:31,
                 from src/kits/app/Application.cpp:50:
/boot/develop/headers/cpp/streambuf.h: In method `ios::~ios()':
/boot/develop/headers/cpp/streambuf.h:485: warning: `void *' is not a 
pointer-to-object type
In file included from /boot/develop/headers/cpp/vector:31,
                 from headers/private/app/LooperList.h:31,
                 from src/kits/app/Application.cpp:50:
/boot/develop/headers/cpp/stl_alloc.h: At top level:
/boot/develop/headers/cpp/stl_alloc.h: In instantiation of 
`__default_alloc_template<false,0>':
/boot/develop/headers/cpp/stl_alloc.h:763:   instantiated from here
/boot/develop/headers/cpp/stl_alloc.h:709: creating array with size 
`_NFREELISTS'

So is this just me having problems?  I assumed it had something to do with the 
header changes, but maybe my system is just borked.

Other related posts: