[openbeosstorage] Re: ddm questions
- From: Tyler Dauwalder <tyler@xxxxxxxxxxxxx>
- To: openbeosstorage@xxxxxxxxxxxxx
- Date: Mon, 27 Oct 2003 00:36:39 -0800
> > > I wouldn't have seen it if you
> > > hadn't used user_strcpy() :-)
> > Now I'm confused. Is/was something not building for you because of
> > the
> > user_strcpy() calls? I seem to have no problem with it over here. And
> > further, I can't see how it's any more unimplemented than
> > user_strlcpy() or
> > user_strncpy(); there seems to be corresponding code for
> > user_strcpy()
> > everywhere there's code for those two functions (unless I'm missing
> > something, which wouldn't be a first ;-).
>
> ... okay, now I am confused as well. I could not build the ddm because
> of user_strcpy() - it said "undefined reference", so I assumed it's not
> part of the kernel.
> But a closer look could have told me that it couldn't build the
> libdisk_device_manager.so only (I just tried again). Maybe our build
> misses a dependency to rebuild the lib that would contain
> user_strcpy()? (it builds now that user_strcpy() is not used anymore,
> though - and libkernelland_emu.so was rebuild as well here - maybe I
> simply forgot to update it [although I think I almost do a cvs update
> twice a day in the root directory...])
I believe libkernelland_emu.so is built properly as a dependency, because,
IIRC, I was using 'jam libdisk_device_manager.so DiskDeviceManagerTest'
while I was making those changes, and libkernelland_emu.so was rebuilt
properly when I added user_strlcpy() to it. So maybe your copy just didn't
get updated properly. Who knows... :-)
> Well, so let's just ignore that, and I will remove user_strcpy() from
> the kernel - thanks for the hint ;-)
Sounds good to me. :-)
-Tyler
Other related posts:
