Re: glibc/eglibc, convert to TI-RPC...

["Yann E. MORIN" <yann dot morin dot 1998 at anciens dot enib dot fr>]

Bill, All,

On Thursday 01 September 2011 21:08:02 Bill Pringlemeir wrote:
> It seems that newer versions of glibc and eglibc use a 'TI-RPC'.  I
> installed a cross ARM with 2.14 and many ltib packages do not build with
> this compiler/toolset.  I googled and couldn't find any how to on
> updating to this version.  If the rpc.h headers are no longer in libc,
> what are you suppose to '#include' in source.  Or are we to alter a
> '-I'?  Is anyone aware of a FAQ/Howto on TI-RPC conversion?  Are there
> RPC api changes or just library and header adjustments?
[--SNIP--]
> For now, I rebuilt with 2.13 but I understand that IPv6 support is
> probably good to have as standard.

I already sent an RFC about two months ago:
  http://sourceware.org/ml/crossgcc/2011-07/msg00014.html

I was suggesting to possiblities:
 - treat RPC as a system feature
    -> we need to add TIRPC to the build
 - treat RPC as a non-system feature
    -> applications that need RPC should depend on TIRPC

But TIRPC is not yet complete, so it is not yet a proper replacement.

The resolution *so far* is, for crosstool-NG:
 - we don't care

If the user requires RPC, then (s)he should use 2.13 or before.

That could well change over time, but one pre-requisite is that TIRPC gets
mature enough to be a proper replacement.

I'd refer you back to my original post for more info

Regards,
Yann E. MORIN.

-- 
.-----------------.--------------------.------------------.--------------------.
|  Yann E. MORIN  | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software  Designer | \ / CAMPAIGN     |  ___               |
| +33 223 225 172 `------------.-------:  X  AGAINST      |  \e/  There is no  |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL    |   v   conspiracy.  |
'------------------------------^-------^------------------^--------------------'

--
For unsubscribe information see http://sourceware.org/lists.html#faq