The mistake was completely on my part, I somehow connected the dots the
wrong way in my head.
The only exceptions (for now) are archivers/zstd and ports-mgmt/synth
which were already picked up by new volunteers in the mean time.
GCC 6.1 was released this week. The Ada Framework in FreeBSD ports has
been based on GCC 5.3 GNAT although GCC 6.x has been supported for awhile
via the ADA_DEFAULT option in make.conf.
Now that GCC 6 has been officially released, switch to it by default.
People can maintain the old foundation by putting "ADA_DEFAULT=5" in
/etc/make.conf.
Libraries built by one GNAT are unusable by another, so almost every Ada
port has been bumped as a result. Noticable exceptions are dns/ironsides
which fails to build on gcc6 (thus USES=ada:5 is set) and cad/ghdl which
needs additional testing as it may require gcc5 on FreeBSD (DragonFly
uses the LLVM backend only).
This port generates some headers based on MySQL headers, and a couple
of the variables must have been deprecated because the resulting
variable name ended in "__UNUSED". Double underscores are not allowed
in Ada, so the build broke.
Since the Ada header is generated during the configure phase, I'm adding
a post-configure target to replace "__" with "_" to restore the build.
Since the dependencies change from MySQL 5.5 to MySQL 5.6, revbump.
Without direction, GPRconfig will create a cgpr file at the standard
$PREFIX/lib/gnat repository. This is the cause of the builder
failures because it touches a part of the userland it's not supposed to.
GPRconfig should be modified not to do this; it is never desirable.
In the meantime, the fix for APQ is to specify .cgpr targets which do
not exist so GPRconfig creates them there instead of $PREFIX/lib/gnat.
Reported by: swills
APQ is a database interface library written in Ada95. This is the base
library, but it is not useful without a driver. There are three drivers
available for PostgreSQL, MySQL, and ODBC in separate ports.
Some features:
* Thick binding
* Strong typing support
* Full BLOB support (PGSQL)
* High performance BLOB I/O via streams
* Full support for NULL Values
* Fully portable (database neutral) code possible
* Four levels of debug tracing
WWW: https://bitbucket.org/kowframework/apq
