On Tue, Apr 19, 2011 at 12:18 AM, Clemens <clemens.zeidler@xxxxxxxxxxxxxx> wrote: > On Tue, 19 Apr 2011 02:58:03 +1200, marius adrian popa <mapopa@xxxxxxxxx> > wrote: > >> On Mon, Apr 18, 2011 at 12:51 AM, Clemens >> <clemens.zeidler@xxxxxxxxxxxxxx> wrote: >>> >>> On Mon, 18 Apr 2011 07:08:34 +1200, marius adrian popa <mapopa@xxxxxxxxx> >>> wrote: >>> >>>> { >>>> - result += $(1)/home/gringo/hack/haiku/haiku/$(i) ; >>>> + result += $(1)/home/mariuz/work/haiku/$(i) ; >>>> } >>>> return $(result) ; >>>> } >>> >>> Should be possible to not hard code the path e.g. use the $(HAIKU_TOP) >>> jam >>> variable... >> >> Ok i will modify it >>> >>>> now i have another conflicting type , but i don't think we need >>>> network related code from linux >> >> Solved by removing net.c >> >> rm lkl-linux-2.6/arch/lkl/envs//lib/net.c >> I will go at home and do some tests >> >> ls -lah >> generated/objects/haiku/x86/release/add-ons/kernel/file_systems/lklhaikufs/lklhaikufs >> -rwxr-xr-x 1 mariuz mariuz 13M Apr 18 10:48 >> >> generated/objects/haiku/x86/release/add-ons/kernel/file_systems/lklhaikufs/lklhaikufs >> >> >> wow image is generated > > cool are you able to mount something? I build now a image on my workstation to mount it under qemu/kvm as ext3 partition > >> >> ls -lah generated/haiku.image >> -rw-r--r-- 1 mariuz mariuz 200M Apr 18 10:49 generated/haiku.image >> >> >>> >>> Seems that you have the haiku src in the header path while building >>> linux, >>> is that necessary? >> >> Yes is needed , linux kernel Library is using functions from >> haiku kernel >> >> saw it in >> ../lkl-linux-2.6/arch/lkl/envs/khaiku.c >> > > I'm not 100% sure but maybe the problem is that a haiku header is included > in a linux/lkl glue code header and so accidentally used for linux too. You > could check if there is such a header and try to move the haiku part to the > according c file... Thanks for the tip I will do in my git branch and propose to be merged upstream