Chase libgmp and bump PORTREVISION.523a16e2bd
Port details
lang/gnustep-base 1.31.1_1
GNUstep Foundation library
Port info
- Maintainer
- joe.maloney@icloud.com
- Packages
- latest: 1.31.1_1
- Upstream
- up to date
- Last update
- to 1.31.1_1 · c168f47362
- Quarterly
- 2026Q4: 1.31.1_1
- WWW
- http://www.gnustep.org/
- Links
- cgit · VuXML · Report wrong data
Install
- Package
# pkg install gnustep-baseinstalls 1.31.1_1 fromlatest; fromquarterly(2026Q4) 1.31.1_1- Port
# cd /usr/ports/lang/gnustep-base && make install clean# make -C /usr/ports/lang/gnustep-base config # change options first
- Size
- 2.2 MiB download · 10 MiB installed
- Depends on
- devel/gnustep-make 2.9.3, devel/icu 76.1,1, devel/libffi 3.8.0, ftp/curl 8.23.0, lang/libobjc2 2.3, math/gmp 6.3.0, net/avahi-app 0.8_6, security/gnutls 3.8.13, security/libgcrypt 1.12.4, textproc/libxml2 2.15.4, textproc/libxslt 1.1.45
- License
- GPLv3 and LGPL3
- Options
- 3 of 4 on in the package: AVAHI GNUTLS ICU
Show the 1 options that are off
MDNS
Packages by version and architecture
latest
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 16 | 1.31.1_1 | 1.31.1_1 | – |
| FreeBSD 15 | 1.31.1_1 | 1.31.1_1 | – |
| FreeBSD 14 | 1.31.1_1 | 1.31.1_1 | 1.31.1_1 |
quarterly (2026Q4)
| FreeBSD version | amd64 | aarch64 | i386 |
|---|---|---|---|
| FreeBSD 15 | 1.31.1_1 | 1.31.1_1 | – |
| FreeBSD 14 | 1.31.1_1 | 1.31.1_1 | 1.31.1_1 |
version as in the ports tree (latest) or the most common one (quarterly) · different version · ✗ not built · – no packages for this platform. Package sets that have not been rebuilt for 60 days are left out.
Unaddressed and VuXML only (0)
No unaddressed CVE and nothing reported by
pkg audit for the packaged version 1.31.1_1.Fixed (0)
No VuXML entries for this package.
Problem reports (1) · open in Bugzilla, most recently changed first
| PR | Summary | Status | Changed |
|---|---|---|---|
| 288847 | lang/gnustep-base: should we put devel/libdispatch into LIB_DEPENDS? | New | 2025-08-13 |
Commits (211)
- set NO_PACKAGE21bef45d60
- update to 1.18.0b4cb3b6756
- update to 1.16.58d54a3338e
- update to 1.16.408c00070a5
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script. Specifically, newer autoconf (> 2.13) has different semantic of the configure target. In short, one should use --build=CONFIGURE_TARGET instead of CONFIGURE_TARGET directly. Otherwise, you will get a warning and the old semantic may be removed in later autoconf releases.
To workaround this issue, many ports hack the CONFIGURE_TARGET variable
so that it contains the ``--build='' prefix.
To solve this issue, under the fact that some ports still have
configure script generated by the old autoconf, we use runtime detection
in the do-configure target so that the proper argument can be used.
Changes to Mk/*:
- Add runtime detection magic in bsd.port.mk
- Remove CONFIGURE_TARGET hack in various bsd.*.mk
- USE_GNOME=gnometarget is now an no-op
Changes to individual ports, other than removing the CONFIGURE_TARGET hack:
= pkg-plist changed (due to the ugly CONFIGURE_TARGET prefix in * executables)
- comms/gnuradio
- science/abinit
- science/elmer-fem
- science/elmer-matc
- science/elmer-meshgen2d
- science/elmerfront
- science/elmerpost
= use x86_64 as ARCH
- devel/g-wrap
= other changes
- print/magicfilter
GNU_CONFIGURE -> HAS_CONFIGURE since it's not generated by autoconf
Total # of ports modified: 1,027
Total # of ports affected: ~7,000 (set GNU_CONFIGURE to yes)
PR: 126524 (obsoletes 52917)
Submitted by: rafan
Tested on: two pointyhat 7-amd64 exp runs (by pav)
Approved by: portmgr (pav)741aa71483Conversion from (now defunct) autoconf-2.61 to autoconf-2.62 Tested by: exp build run (erwin)771ea13f41
- udpate stable to 1.16.3ab0b73a674
- update to 1.16.30a1d7f13f4
- update to 1.16.2c7ccb5c6b5
- update to 1.16.098ae4f0749
- update to 1.14.43383ed4b4f
- add WITH_GNUSTEP_DEVEL1b9f926d36
- update to 1.14.3b6a52153d4
- update to 1.14.22412099627
Switch autoconf dependencies from 2.53 or 2.59 to 2.61. PR: ports/116639 Submitted by: aDe48420a5ebd
- update to 1.13.1cdc1aa019f
Retire NO_FILTER_SHLIBS now that it no longer serves a purposea01439c2ca
- update to use new bsd.gnustep.mk Approved by: gurkan@linuks.mine.nud7f59ea8de
- update to 1.13.093405b24d1
- remove LDCONFIG_GCC workaroundc3d379c79d
- activate regression-testfa1045dda1
- make sure ldconfig has been run2995a979d5
- make portlint happier1a4bb222f5
Chase gmp library and bump PORTREVISION.ffcb54b54f
- cleanup after gcc updates no hacks for ldconfig needed8d7e99571b
- add USE_GNUSTEP_PREFIXccd3e4a8d4
- update to 1.12.014f10b4598
- new option GNUSTEP_PREFIX allow user defined location of all files3b6641a158
- enable fake-main support again so packages can be build without procfs - new option WITHOUT_GNUSTEP_FAKEMAIN1d306ef3e3
- update to 1.11.233caebc6a9
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.54a0b86543
- add SHA checksumec997a9574
- update to 1.11.1f07a57f9f4
- cleanup Makefile locatione99d7a1173
- update to 1.10.0a69d82a06f
- new option WITH_GNUSTEP_FAKEMAIN to work without procfs - call ldconfig in configure stage again this workarounds a problem that ldconfig is called to early when addding a package like: gcc-objc-current-3.3.6_20050511.tgz8eafc28228
- update to 1.10.38521b5b156
- remove WITH_GNUSTEP_DEVEL - update to 1.10.209bb2ae21d
- cleanup Makefile3e06360037
- update to 1.10.1 (stable)e5e0cea40b
- update to 1.10.0 (stable)811cff3000
- Fix PATH problem with bsd.autotools.mk PR: 64393ab630c8e5e
- update to 1.9.2aa3074a492
- patch to fix coredumps in make_servicese63ab851d0
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.3f651573ad- update to 1.9.194806b5b2a
- add SIZEc600b83191
Bump PORTREVISION on all ports that depend on gettext to aid with upgrading. (Part 2)053fdb6a6b
- update MASTER_SITES6abdfa6dbb