FreeLists / openbeosnetteam / [openbeosnetteam] Re: Some quick questions

[Philippe Houdoin <philippe.houdoin@xxxxxxx>]

Hi Oliver,

> Many thanks for your guidance through the building of the userland tools,
> using that info, I now have it running here.
>
> > Anyway:
> >
> > 1) First, build the net_server_driver
> >
> > $ cd src/add-ons/kernel/drivers/net/stack
> > $ jam net_server_driver
>
> This worked.
>
> > 2) Second, build the userland net_stack_tester app and the network stack
> > modules in their userland version (aka plain add-ons, not kernel add-ons):
> >
> > $ cd src/tests/add-ons/kernel/network
> > $ jam
>
> This didn't work, but now I've added the legacy (and posix) headers, it does.

Yeah, I should have know that. When I commit my fixes to unbreak the build of
userland version, I was wondering how I could check the build for the "bone"
target, not only "haiku". But from the office, I'm building on Linux, aka only
for haiku (but x86 or ppc!).
When I came back to home that day, I forgot to check on a BeOS system!
My bad. Sorry.

> Yep, I manually recreated the required subfolder layout, but I'd like to
> create a new jam-rule to do that, as it's a bit tedious, otherwise...

Indeed. I'm definitively a bad jammer, and a lazy one!

> I had to create a 'lib'-folder next to each tool I tested, as otherwise, it
> would try to link to BONE's libsocket.so. After I pointed tools to the right
> lib, ifconfig and route worked, but ping didn't (missing icmp). I'll
> investigate about that tomorrow.

IIRC, the "missing icmp" error was due to incomplete /etc/protocols text file.
Check yours against the one we check in SVN.

> > 5) Come back here in hurry and yiel at me that these instructions doesn't
> > work at all.
>
> No yelling, just praise >:o)

I cross my fingers it still be the case in the next days ;-)

- Philippe