Re: Glibc-2.18

On Mon, Sep 1, 2014 at 8:43 PM, Egil Brendsdal <[email protected]> wrote:

> Is it possible to figure out how the pre-installed glibc-2.18 has been
> configured in Gobo 015? What I suspect is that rpc-support isn't enabled
> by the configure option --enable-obsolete-rpc,
> (see http://upstream-tracker.org/changelogs/glibc/2.18/changelog.html):
>
> "New configure option --enable-obsolete-rpc makes the deprecated RPC
> headers and functions available at compile time as they were before
> version 2.14.  This option will be removed at some time in the future
> after the TI-RPC library becomes fully sufficient for the needs of
> existing applications."
>
> As Gobo 015 is now, I doubt any RPC applications can be built based on the
> TI-RPC library.
>
> Regards, Egil.
>
>
Hi Egil,

We have used the JHALFS (Automated Linux From Scratch) script to bootstrap
015. The instructions used to build Glibc were automatically extracted from
the following page:

http://www.linuxfromscratch.org/lfs/view/7.4-rc2/chapter05/glibc.html

So, indeed, the --enable-obsolete-rpc flag was not passed to Glibc's
configure script. I have been using LibTIRPC as a replacement to the
obsolete headers just fine. The caveat is that sometimes the projects
relying on those headers need to have their Makefiles adjusted so that
"-ltirpc" is passed to LDFLAGS.

Best regards,
Lucas

_______________________________________________
gobolinux-users mailing list
[email protected]
http://lists.gobolinux.org/mailman/listinfo/gobolinux-users