XML-RPC is a quick-and-easy way to make procedure calls over the Internet.
It converts the procedure call into XML document, sends it to a remote
server using HTTP, and gets back the response as XML.
This library provides a modular implementation of XML-RPC for C and C++.
- C API and experimental C++ API.
- Modular XML-RPC core: If you want, you can supply all your own HTTP
code.
- Synchronous and asynchronous XML-RPC clients based on w3c-libwww.
- Multithreaded XML-RPC server based on the Abyss web server.
- Full support for basic types, including <struct>, <array> and <base64>.
- Extensive test suites to help verify correct behavior and correct
error handling.
- Passes the official XML-RPC validator1 test suite.
===> The following configuration options are available for xmlrpc-c-1.64.03_1:
CPLUSPLUS=on: Build xmlrpc-c C++ wrapper classes and tools
CURL=on: Build the curl client transport
DEBUG=off: Build with debugging support
LIBWWW=on: Build the libwww client transport
===> Use 'make config' to modify these settings
net/xmlrpc-c: Use canonical WWW URL
Follow the upstream redirect to its canonical location.
While here, pet portclippy
Sponsored by: Rubicon Communications, LLC ("Netgate")
net/xmlrpc-c: Fix parallel build
The build races with itself: lib/openssl links libxmlrpc_openssl.so
while
lib/libutil is still linking libxmlrpc_util.so. With the symlink
missing,
the linker falls back to the static libxmlrpc_util.a, whose objects are
not
PIC:
ld: error: relocation R_X86_64_PC32 cannot be used against symbol
'__stack_chk_guard'; recompile with -fPIC
>>> asprintf.o:(xmlrpc_asprintf) in archive
.../lib/libutil/libxmlrpc_util.a
Setting MAKE_JOBS_UNSAFE makes the build deterministic.
PR: 298187
Approved by: garga (maintainer)
Sponsored by: Netzkommune GmbH
net/xmlrpc-c: Update to 1.59.02
While here, remove some unneeded code from post-extract and simplify
DEBUG option change to CFLAGS
Sponsored by: Rubicon Communications, LLC ("Netgate")
*/*: Update WWW to use HTTPS for sourceforge.net projects
Homepage link is permanent redirected to its HTTPS counterpart
Issue reported by repology : https://repology.org/repository/freebsd/problems
Approved by: portmgr (blanket)
PR: 274888
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
net/xmlrpc-c: Update dependencies
After r473964, expat source code is no longer present in the libwww tree.
Reported by: Q/A tests
Approved by: garga (maintainer)
www/libwww: Update to 5.4.2, Fix security vulnerabilities
This a security release for libwww to take into account security advisories
CVE-2016-9063 and CVE-2017-9233.
In order to take into account current and future expat security advisories,
the expat source code was removed from the libwww tree. The makefiles were
modified so that libwww dynamically links against the system's expat library.
Patches removed were incorporated upstream.
Bump PORTREVISION of dependent ports due shlib change.
Changes: libwww/5.4.2/ChangeLog" REL="NOFOLLOW">https://raw.githubusercontent.com/w3c/libwww/5.4.2/ChangeLog
MFH: 2018Q3
Security: e375ff3f-7fec-11e8-8088-28d244aee256
net category: Remove $PTHREAD_LIBS
openafs did not pass check-plist (pre-existing) so fixed and bumped.
Also, pkg-plist was sorted. mediatomb and spread also fail plist-checks
but they weren't fixed.
approved by: PTHREAD blanket
Remove USE_GNOME=gnometarget from ports. It has been a empty keyword since
mid 2008.
PR: ports/159624
Submitted by: Ruslan Mahmatkhanov <cvs-src@yandex.ru>
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22.
-Update libtool and libltdl to 2.2.6a.
-Remove devel/libtool15 and devel/libltdl15.
-Fix ports build with libtool22/libltdl22.
-Bump ports that depend on libltdl22 due to shared library version change.
-Explain what to do update in the UPDATING.
It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop
and applications in the runtime.
With help: marcus and kwm
Pointyhat-exp: a few times by pav
Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and
a few MarcusCom CVS users. Also, I might have missed a few.
Repocopy by: marcus
Approved by: portmgr
Bump the version of the curl shared library after the ftp/curl update
to 7.19.2.
Bump PORTREVISION, even on the ports that do not have a versioned
dependency, since the binaries will most probably still stop working.
Before bsd.port.pre.mk, set either USE_PERL5 or WANT_PERL, depending on
whether the perl dependency is unconditional or conditional. This will
be needed for the conditional inclusion of bsd.perl.mk.
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present
in bsd.autotools.mk essentially makes this a no-op given that all the
old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in
exactly the same way as USE_AUTOTOOLS itself.
Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME
team -- all GNOME 2.12.x ports use it.
Preliminary documentation can be found at:
http://people.FreeBSD.org/~ade/autotools.txt
which is in the process of being SGMLized before introduction into the
Porters Handbook.
Light blue touch-paper. Run.
Apply a big libtool patch to allow porters to use the libtool installed by
the libtoolX ports instead of the one included with each port. Ports that
set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of
the included version. To restore previous behavior, use the new macro,
USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version.
For example, to use the ports version of libtool-1.5, add the following to
your Makefile:
USE_LIBTOOL_VER= 15
To use the included version of libtool with extra hacks provided by
libtool-1.5, add the following to your Makefile:
USE_INC_LIBTOOL_VER= 15
With this change, ports that had to add additional libtool hacks to prevent
.la files from being installed or to fix certain threading issues can now
delete those hacks (after appropriate testing, of course).
PR: 63944
Based on work by:eik and marcus
Approved by: ade (autotools maintainer)
Tested by: kris on pointyhat
Bound to be hidden problems: You bet
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.