Bug 460730 – dev-libs/xmlrpc-c - USE=tools disappeared

• Product: Gentoo Linux
• Status: RESOLVED FIXED

[Description Patrick 2013-03-07 22:04:34 UTC]

Could you please bring back the 'tools' USE flag? I updated xmlrpc-c, and suddenly my shell script stops working, because the binary (that comes with USE=tools) is missing.

On the xmlrpc-c changelog website (http://xmlrpc-c.sourceforge.net/change.html) it says "Build: remove --enable-tools option added in 1.18. User can just do 'make -C tools ' or 'make all' to get that."

Thanks!

Reproducible: Always

Steps to Reproduce:
1. Update xmlrpc-c from 1.28.03-r1 to 1.32.05
2. Try to call 'xmlrpc' on the command line

Actual Results:  
# xmlrpc
bash: xmlrpc: command not found

Expected Results:  
/usr/bin/xmlrpc is present

[Comment 1 dtr 2013-03-29 20:55:55 UTC]

Second this, tools disappeared with update.

[Comment 2 Mikle Kolyada (RETIRED) 2013-03-30 06:05:20 UTC]

Does not CC arch teams

[Comment 3 Andreis Vinogradovs ( slepnoga ) 2013-04-07 08:43:06 UTC]

This code from configure.in:
 99 BUILD_XMLRPC_PSTREAM=no
100
101 if ! test "$MUST_BUILD_WININET_CLIENT $MUST_BUILD_CURL_CLIENT $MUST_BUILD_LIBWWW_CLIENT" = "no no no"; then
102   if test $have_libreadline = yes && test $have_libncurses = yes; then
103     BUILD_XMLRPC_PSTREAM=yes
104   fi
105   BUILD_TOOLS=yes
106 else
107   BUILD_TOOLS=no
108 fi
109
110 AC_MSG_RESULT($BUILD_TOOLS)
111 AC_SUBST(BUILD_TOOLS)
112
113 if test $BUILD_TOOLS = yes; then
114   AC_MSG_CHECKING(whether to build the xmlrpc_pstream tool)
115   AC_MSG_RESULT($BUILD_XMLRPC_PSTREAM)
116   AC_SUBST(BUILD_XMLRPC_PSTREAM)
117 fi

Configuration logic is designed so that no library libwww tools will not compile.
dev-libs/libwww dropped from tree due GBZ #409549 and #320253
I think that to WONTFIX;

Please, open new bug a change in the upstream

[Comment 4 Alexander Vershilov (RETIRED) 2013-05-27 11:19:14 UTC]

new revision: 1.155; previous revision: 1.154

[Comment 5 Alexander Vershilov (RETIRED) 2013-05-27 11:19:46 UTC]

Fixed in new revision: 1.155; previous revision: 1.154

The problem was in changed build rules.

[Comment 6 Jeroen Roovers (RETIRED) 2013-05-31 13:49:29 UTC]

*** Bug 471902 has been marked as a duplicate of this bug. ***