[haiku-development] Re: Haiku Userland on Non-Haiku Kernel
- From: Adrien Destugues <pulkomandy@xxxxxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Wed, 18 Feb 2015 11:36:08 +0100
On Wed, Feb 18, 2015 at 11:21:33AM +0100, Stephan wrote:
> Hi
>
> Thank you very much. I downloaded cosmoe and - after making some
> changes to the code - could compile it on NetBSD 6.0 amd64. Worst
> problem was the absence of semtimedop(). The appserver works already
> in SDL mode, but registrar is unable to start:
I'm not sure this code was tested out of 32-bit mode - I would start
with a 32-bit x86 system first if possible.
>
> appserver:
> ========================
> initialize_before()
> initialize_before() done
> FontServer::ScanDirectory(): opening /usr/share/fonts/ttf/cosmoe
> FontServer::ScanDirectory(): found entry .
> FontServer::ScanDirectory(): found entry ..
> FontServer::ScanDirectory(): found entry Vera.ttf
> FontServer::ScanDirectory(): found entry VeraBI.ttf
> FontServer::ScanDirectory(): found entry VeraBd.ttf
> FontServer::ScanDirectory(): found entry VeraIt.ttf
> FontServer::ScanDirectory(): found entry VeraMoBI.ttf
> FontServer::ScanDirectory(): found entry VeraMoBd.ttf
> FontServer::ScanDirectory(): found entry VeraMoIt.ttf
> FontServer::ScanDirectory(): found entry VeraMono.ttf
> FontServer::ScanDirectory(): found entry VeraSe.ttf
> FontServer::ScanDirectory(): found entry VeraSeBd.ttf
> FontServer::ScanDirectory(): found entry code_alt.ttf
> Directory '/usr/share/fonts/ttf/cosmoe' scanned, 11 fonts found
> Desktop: InitDesktop
> SDLDriver constructor
> Loading SDL Driver...
> ========================
> (a black window appers then)
>
> registrar:
> ========================
> initialize_before()
> initialize_before() done
> REG: main()
> BUG: Looper must be locked before calling AddHandler.
> BApplication 1 called
> 1: fInitError = 0
> 2: fInitError = -9223372036854775801
> 3: fInitError = -9223372036854775801
> 4: fInitError = -9223372036854775801
There are errors at this point already - I guess fInitError is supposed
to stay 0 when everything goes fine. It seems someone already added some
traces to investigate that problem?
> 5: be_app and be_app_messenger
> 6: _init_interface_kit_
> info: LinkMsgSender buffered header AS_CREATE_BCURSOR [0 1601401488 0].
> info: LinkMsgSender Flush() waiting to send 1 messages of 100 bytes on port
> -1.
> error info: LinkMsgSender Flush() failed for 100 bytes (Unknown error:
> 4608) on port -1.
And here it apparently fails to communicate with the app_server trying
to create the main cursor (for the mouse).
> info: LinkMsgSender buffered header AS_CREATE_BCURSOR [0 1601401488 0].
> info: LinkMsgSender Flush() waiting to send 1 messages of 100 bytes on port
> -1.
> error info: LinkMsgSender Flush() failed for 100 bytes (Unknown error:
> 4608) on port -1.
> 7: cursors created
> App could not initialize due to error (-9223372036854775801)
> teardown_threads(): 0 threads deleted
> terminate_after()
> terminate_after() done
> teardown_ports(): 0 ports deleted
> ========================
>
> Any hint where to look is appreciated :)
I think Ithamar is around on this list, let's see if he can help :)
--
Adrien.
Other related posts:
