Recent versions of gettext no longer install m4 files in
PREFIX/share/aclocal. They have to be installed in the work
directory by autopoint for aclocal to find them.
Patch devel/autoconf so autoreconf runs autopoint when gettext related
macros are used in configure.ac (e.g. AM_ICONV). Previously it only
ran autopoint when AM_GNU_GETTEXT_(REQUIRE_)VERSION was used.
The following ports now require autopoint (i.e. USES=gettext-tools):
benchmarks/sysbench, devel/libhtp, editors/fxite, filesystems/rar2fs,
graphics/gd, net/ucarp, news/fidogate, sysutils/cdrdao
Other fixes:
emulators/mednafen, misc/lifelines: Use older version of gettext macros.
ftp/axel: Patch Makefile.am and configure.ac to get gettext working and
add NLS option.
ftp/wzdftpd: Use autoreconf 2.72.
mail/sympa: Remove hack from configure.ac.
multimedia/dvdauthor: Use ports autoreconf.
net/asterisk-chan_sccp: Drop autoreconf and gettext-tools dependencies.
security/pam_pkcs11: Patch configure.ac so autoreconf can find the
custom directory with m4 files.
sysutils/grub2-efi, sysutils/grub2-pcbsd: Add patch to run autoreconf
with -f flag so it updates all files.
www/wget2: Patch configure.ac to what autopoint expects.
PR: 287167
Exp-run by: antoine
A new uses 'sudo' has been added to transperently depends of the
proper flavor of sudo 'default' or 'sssd' depending on the default
version set by the user.
If you prefere to use 'sssd' flavor of sudo, add the following
to your make.conf:
DEFAULT_VERSIONS+=sudo=sssd
All sudo consummer ports has benn updated to USES=sudo
Reviewed by: 0mp
Approved by: mat
Sponsored by: Klara, Inc.
Differential Revision: https://reviews.freebsd.org/D52160
This reverts commit f95a776840b0d53d446a8f219ed6ed5a7b135029.
As discussed with jbeich, this fix may fix the build, but it doesn't
lead to a working port. Revert until a proper fix can be designed.
MFH: 2025Q4
This fixes the build on armv7, avoiding a bogus int conversion
warning. While we are at it, turn static REINPLACE_CMD usage
into patch file as per policy.
Approved by: portmgr (build fix blanket)
MFH: 2025Q4
- Source code had been reorganized upstream, so the paths to
various files we patch had changed
- The `pithy' codec had been removed because it is very bad
with incompressible data (doesn't fit to allocated buffers)
Reported by: portscout
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.
Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.
Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.
Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.
PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
