Re: Glibc-2.18

Lucas C. Villa Real <lucasvr <at> gobolinux.org> writes:

> I have been using LibTIRPC as a replacement to the obsolete headers just fine.


I still doubt using LibTIRPC as a replacement for the pre glibc-2.14 rpc.
   
Firstly, why does GNU provide --enable-obsolete-rpc which will be
removed when, as they say, after the TI-RPC library becomes fully sufficient.
(By the way, the link is
 http://upstream-tracker.org/changelogs/glibc/2.18/changelog.html
Sorry for the typo in the link, I'm not familiar with how the message text
is processed.)

Secondly, libtirpc is not used in the musl project: "I've given up on
getting libtirpc to work;"
http://www.openwall.com/lists/musl/2012/12/24/1

And, finally, I have not even been able to get the plain old ypbind running
when linking against libtirpc, neither on Gobo 014 nor on Gobo 015. On Gobo
014, portmap, ypbind and autofs runs flawlessly, but all of these were
linked against glibc-2.5. On Gobo 015 I'm stuck. The recipe for Glibc 2.12.1
fails and there's no recipe available for Glibc 2.18.

My question is, then: Is it possible to upload a recipe for Glibc 2.18?
It would be nice to use it as a template for a local recipe and try out
the --enable-obsolete-rpc configure option.

Best regards,
Egil.