Nathan Hawkins <[EMAIL PROTECTED]> wrote: > >The problem I'm having is that I can't get freebsd sources to build on >top of glibc. The library and utility sources that I need seem to be >wanting a lot of stuff that simply isn't in the glibc headers.
It would be nice if some of the bloat in glibc went to providing good APIs :-) The absence of strlcat on Linux is repeatedly irritating. What other things are missing? >Some combination of option 1 and 2 seems most likely to work. I think >we're going to need to be able to use libraries like libkvm with glibc. >I'd been thinking of writing a python wrapper for libcam, and at least >cdrecord will want libcam also. libkvm ought to be obsolete by the time you release, apart from in the context of examining kernel core dumps -- ps/top/etc. will all use sysctl on running kernels. >What concerns me most is that any changes I make to FreeBSD sources to >get them working with glibc will probably not be acceptable upstream, >which poses a large maintenance problem. Of course it depends on the nature of the changes. Conditionally compiling without libkvm (say) could be construed as a feature, but avoiding strlcat would be a waste of time. Tony. -- f.a.n.finch <[EMAIL PROTECTED]> http://dotat.at/ HUMBER: SOUTHWEST 4 OR 5 VEERING NORTHWEST 3 OR 4. RAIN THEN SHOWERS. GOOD OCCASIONALLY MODERATE. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
