Pointless #ifdef maze that ends up on an error if the architecture is
not known:
- POCO_ARCH is only used to get a string representation of the current
architecture (not all known archs benefit from this anyway). On POSIX
systems uname(3) can be used for this.
- POCO_ARCH_LITTLE_ENDIAN/BIG_ENDIAN could be discovered using <endian.h>
or a runtime test.
Upstream commit:
26fa1b9e6b
some existing COMPILER lines with arch restrictions etc. In the usual
case this is now using "COMPILER = base-clang ports-gcc base-gcc" on
ports with c++ libraries in WANTLIB.
This is basically intended to be a noop on architectures using clang
as the system compiler, but help with other architectures where we
currently have many ports knocked out due to building with an unsuitable
compiler -
- some ports require c++11/newer so the GCC version in base that is used
on these archirtectures is too old.
- some ports have conflicts where an executable is built with one compiler
(e.g. gcc from base) but a library dependency is built with a different
one (e.g. gcc from ports), resulted in mixing incompatible libraries in the
same address space.
devel/gmp is intentionally skipped as it's on the path to building gcc -
the c++ library there is unused in ports (and not built by default upstream)
so intending to disable building gmpcxx in a future commit.
a new libmysqlclient non-blocking API which utilizes co-routines. The X86
specific GCC ASM co-routine support hid the fact that there was an issue.
The only fallback code so far is POSIX user contexts which OpenBSD does not
support.
Input from and Ok sthen@ jasper@
a patch from Gentoo.
While there clean up Makefile a bit (mixed whitespace format ugliness) and
simplify a patch (just use upstream's existing sysconf code, rather than
workaround the unportable use of sysctlbyname).
POCO C++ libraries for network based applications
C++ class libraries for network-centric, portable applications,
integrated perfectly with the C++ Standard Library. Includes
network protocols (Sockets, HTTP, FTP, SMTP, POP3, etc.) and an
XML parser.
With a lot of feedback from landry@
Finally OK from dcoppa@
