Source-Changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: src
"Perry E. Metzger" <perry%piermont.com@localhost> writes:
> Klaus Klein <kleink%reziprozitaet.de@localhost> writes:
> > "Perry E. Metzger" <perry%piermont.com@localhost> writes:
> >
> > > If they're kernel calls, shouldn't they be in libc with all the other
> > > kernel calls? Is librt a POSIX mandated thing?
> >
> > [Realtime option interfaces] _may_ be made available by an
> > implementation's default linker operation, but a portable application
> > must not rely on this.
>
> So what is the argument for having it in a separate library when POSIX
> does not mandate that?
Considering the recurring discussions about "too much crud in libc",
that's a funny question to ask.
> Do Solaris and Linux use a librt?
Yes. (But see also see Ben's comment wrt. this particular case.)
- Klaus
Home |
Main Index |
Thread Index |
Old Index