Given the header files and shared objects corresponding to two different shared
library versions, and a simple description of each of the shared libraries in
XML format, abi-compliance-checker searches for the following kinds of binary
compatibility problems:
--added/withdrawn interfaces (functions, global variables)
--changes to constants
--problems in data types:
--classes: added/withdrawn virtual functions (changes in layout of
virtual table), virtual function positions, virtual function
redefinitions
--structural data types: added/withdrawn members (changes in layout of
type structure), changes in members, size changes
--enumerations: member value changes
--interface problems:
--parameter and return type changes
--incorrect symbol versions
The checker then generates a report that assesses the risks of any potential
problems detected.
===> The following configuration options are available for abi-compliance-checker-2.3:
DOCS=on: Build and/or install documentation
PORTS_BINUTILS=off: Use binutils from ports
===> Use 'make config' to modify these settings
*/*: Sunset 12.4-RELEASE/12-STABLE from ports tree
- Remove all references to defunct ARCH arm
- Remove all references to defunct ARCH sparc64
- Remove x11-drivers/xf86-video-sunffb which requires defunct sparc64
ARCH
- Remove sysutils/afbinit requires defunct sparc64 ARCH
- Remove all references to bktr driver
- Remove all references to defunct FreeBSD_12
- Remove all references to OSVERSION/OSREL corresponding to 12
- Remove conditionals in Mk/Uses/cabal.mk
- Remove sparc reference from Mk/Uses/qt-dist.mk
- Remove BROKEN_sparc64/NOT_FOR_ARCH=sparc64
- Remove BROKEN_FreeBSD_12* from:
- Remove OpenSSL patches from:
- Remove conditional flags for OSVERSION >= 1300000 to fixed flags.
Also move conditional flags for non sparc64/arm ARCH to fixed flags.
Reviewed by: brooks, jbeich, rene, salvadore
Differential Revision: https://reviews.freebsd.org/D42068
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 )
devel: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* "Waitman Gobble" <uzimac@da3m0n8t3r.com>
* <jkoshy@FreeBSD.org>
* Aaron Dalton <aaron@FreeBSD.org>
* Aaron Dalton <aaron@daltons.ca>
* Aaron H. K. Diep <ahkdiep@gmail.com>
* Aaron Hurt <ahurt@anbcs.com>
* Abel Chow <abel_chow@yahoo.com>
* Adam McLaurin
* Adam Saponara <as@php.net>
* Adam Weinberger <adamw@FreeBSD.org>
* Ade Lovett <ade@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
Update devel/abi-compliance-checker to recent releases
There was an important release of abi-dumper with fixes
in November 2020; otherwise the compatibility results using
"new" style are bogus.
Not taking this port as I don't think it's useful enough on FreeBSD;
clang-compatibility is an issue and parts of the tool demand
gcc 4.5.8 (the port doesn't handle that gracefully either).
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
Update devel/abi-compliance-checker to the current git snapshot.
The script now depends on two tools abi-dumper and vtable-dumper. The
only purpose of the tools is to provide neccessary services to the
abi-compliance-checker, so I included all of them into the updated
port, instead of providing dependencies.
Sponsored by: The FreeBSD Foundation
Reviewed, tested and approved by: ehaupt
Differential revision: https://reviews.freebsd.org/D9315
Bump PORTREVISIONS for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.8.5 to GCC 4.9.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
In particular that is ports with USE_GCC=yes, USE_GCC=any, or one of
gcc-c++11-lib, openmp, nestedfct, c++11-lib as well as c++14-lang,
c++11-lang, c++0x, c11 requested via USES=compiler.
According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.
This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.
Approved by: portmgr (bapt)
Given the header files and shared objects corresponding to two different shared
library versions, and a simple description of each of the shared libraries in
XML format, abi-compliance-checker searches for the following kinds of binary
compatibility problems:
--Added/withdrawn interfaces (functions, global variables)
--Problems in Data Types:
--Classes: added/withdrawn virtual functions (changes in layout of
virtual table), virtual function positions, virtual function
redefinitions
--Structural data types: added/withdrawn members (changes in layout of
type structure),
changes in members, size changes
--Enumerations: member value changes
--Interface problems:
--Parameters and return type changes
--Static property changes
The checker then generates a report that assesses the risks of any potential
problems detected.
WWW: http://ispras.linux-foundation.org/index.php/ABI_compliance_checker
PR: ports/138094
Submitted by: bf <bf1783 at gmail.com>
