[PATCH] Make sunrpc code available for building again

[Mike Frysinger]

On Thursday 10 May 2012 14:12:02 Andreas Jaeger wrote:
> On 05/09/2012 06:43 PM, Mike Frysinger wrote:
> > On Wednesday 09 May 2012 16:24:41 Andreas Jaeger wrote:
> >> --- a/configure.in
> >> +++ b/configure.in
> >> @@ -252,6 +252,17 @@ else
> >> 
> >>   fi
> >>   AC_SUBST(libc_cv_nss_crypt)
> >> 
> >> +AC_ARG_ENABLE([obsolete-rpc],
> >> +              AC_HELP_STRING([--enable-obsolete-rpc],
> >> +                             [build and install the obsolete RPC code
> >> for link-time usage]),
> > 
> > should we mention ti-rpc ?  or is that overkill ?
> 
> In the NEWS entry. Or do you have an idea for a good wording?

we could have it warn at configure time:

--- a/configure.in
+++ b/configure.in
@@ -260,6 +260,7 @@ AC_ARG_ENABLE([obsolete-rpc],
 AC_SUBST(link_obsolete_rpc)
 
 if test "$link_obsolete_rpc" = yes; then
+  AC_MSG_WARN([enabling obsolete RPC; consider using the TI-RPC project instead])
   AC_DEFINE(LINK_OBSOLETE_RPC)
 fi
 
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
URL: <http://sourceware.org/pipermail/libc-alpha/attachments/20120514/0a44eef2/attachment.sig>