The Sigar API provides a portable interface for gathering system information
such as:
* System memory, swap, cpu, load average, uptime, loginsi
* Per-process memory, cpu, credential info, state, arguments, environment,
open files
* File system detection and metrics
* Network interface detection, configuration info and metrics
* TCP and UDP connection tables
* Network route table
This information is available in most operating systems, but each OS has their
own way(s) providing it. SIGAR provides developers with one API to access this
information regardless of the underlying platform. The core API is implemented
in pure C with bindings currently implemented for Java, Perl, Ruby, Python,
Erlang, PHP and C#. This port provides the Java bindings.
java/sigar: remove run_depends
this port is only used as a library
the final application decides what JDK is used
by removing RUN_DEPENDS we prevent installing an unused extra openjdk
Approved-by: no maintainer
java/sigar: fix running with openjdk8
Running Cassandra 3 gave:
java.lang.UnsupportedClassVersionError: org/hyperic/sigar/SigarException has
been compiled by a more recent version of the Java Runtime (class file version
65.0), this version of the Java Runtime only recognizes class file versions up
to 52.0
PR: 294323
Reported-by: Lapo Luchini
Fixes: f3a12dc72aa72af22212e3e37c5f29652eae0cbb "fix compilation with jdk21"
MFH: 2026Q2
Pointy-hat: to me
java/sigar: fix build on powerpc
install:
/wrkdirs/usr/ports/java/sigar/work/sigar-6719d4d/bindings/java/sigar-bin/lib/libsigar-powerpc-freebsd-1.so:
No such file or directory
Mk/**java.mk: Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
java/sigar: enable on armv6 and armv7
builds and packages fine
does not touch existing architectures
it was marked broken in 2017 without mention of the error message
FreeBSD and OpenJDK had quite some improvements since 2017
Approved by: port has no maintainer
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 )
java: remove 'Created by' lines
A big Thank You to the original contributors of these ports:
* Alex Dupre <ale@FreeBSD.org>
* Alex Semenyaka <alex@rinet.ru>
* Alexander Yerenkow <yerenkow@gmail.com>
* Anton Yudin (<contact@toha.org.ua>)
* Anton Yudin <toha@toha.org.ua>
* Benjamin Close <benjsc@FreeBSD.org>
* Björn König <bkoenig@alpha-tierchen.de>
* Conor McDermottroe <ports@mcdermottroe.com>
* Danilo Egea Gondolfo <danilo@FreeBSD.org
* Dave Glowacki <dglo@ssec.wisc.edu>
* Ernst de Haan <znerd@FreeBSD.org>
(Only the first 15 lines of the commit message are shown above )
java/sigar: the port had been updated and improved (+)
- Switch (temporarily?) to somewhat more developed GitHub fork
- Add Java 11 support, `do-test' target, and remove GCC dependency
- Optimize away PLATFORM_VER variable and just set the LIBNAME (without
the suffix to make it more obvious that it's a shared object when we
install things, and in the PLIST_FILES)
- Utilize BUILD_WRKSRC and introduce INVOKE_ANT variable to reduce the
tautology in targets' recipes
- When symlinking to ${CC} as local compiler, do not assume it lives as
${LOCALBASE}/bin/${CC} and call `which ${CC}` explicitly
- Garbage-collect commented out `post-patch' target while we're here
PR: 245867
Submitted by: Angelo Polo
*/*: Replace USE_GCC=any with USE_GCC=yes
USE_GCC=any has been equivalent to USE_GCC=yes in most cases (such
as i386 and amd64 since 12.x and depending on configuration 11.x,
most newer installations on other platforms, and 13.x across the
board).
Since commit 96c17633d90386b5bcf8 Mk/bsd.gcc.mk is treating them as
different spellings of the same, so continue the deorbiting of the
USE_GCC=any form and simply replace it with USE_GCC=yes.
This should not make any functional difference at all.
Discussed with: mat, linimon, pkubaj
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
Bump PORTREVISION for ports depending on the canonical version of GCC
in the ports tree (via Mk/bsd.default-versions.mk and lang/gcc) which
has now moved from GCC 6 to GCC 7 by default.
This includes ports
- featuring USE_GCC=yes or USE_GCC=any,
- featuring USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and those
- with USES=compiler specifying one of openmp, nestedfct, c11, c++0x,
c++11-lib, c++11-lang, c++14-lang, c++17-lang, or gcc-c++11-lib.
PR: 222542
For ports that are marked BROKEN on armv6, and also fail to build on
armv7, mark them so.
This is part two of a multipart commit to bring armv7 ports to parity
with armv6.
Approved by: portmgr (tier-2 blanket)
Obtained from: lonesome.com -exp run
Bump PORTREVISION for ports depending on the canonical version of GCC
(via Mk/bsd.default-versions.mk and lang/gcc) which has moved from
GCC 5.4 to GCC 6.4 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, c++11-lib, c++11-lang,
c++14-lang, c++0x, c11, or gcc-c++11-lib.
PR: 219275
Bump PORTREVISIONs for ports depending on the canonical version of GCC and
lang/gcc which have moved from GCC 4.9.4 to GCC 5.4 (at least under some
circumstances such as versions of FreeBSD or platforms).
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using using Mk/bsd.octave.mk which in turn has USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c++11-lib, c++14-lang,
c++11-lang, c++0x, c11, or gcc-c++11-lib.
PR: 216707
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.
- Disable ccache for this port: it fails to build by not respecting the
environment:
[cc] ccache: error: Failed to create directory /nonexistent/.ccache/tmp:
Permission denied
Approved by: portmgr blanket
java/sigar: Fix typo from previous commit (LATFORM => PLATFORM)
While here, replace "freebsd" in LIBNAME with ${OPSYS:tl} to facilitate
DragonFly support.
Approved by: Just fix it
Remove OSVERSION checks that do not make sense any more.
For example (${OSVERSION} >= 900000 && ${OSVERSION} < 900021) is always true,
as is (${OSVERSION} > 900002 || ${OSVERSION} < 900000 && ${OSVERSION} > 800107).
Regarding patches, when an EXTRA_PATCHES is no longer needed, I remove it, when
it is always needed, I renamed it, in one case, I merged two patches.
Differential Revision: https://reviews.freebsd.org/D2209
Update USE_GITHUB so it does not require GH_COMMIT.
Using this new scheme allows only setting the _tag_ or _commit hash_ in
GH_TAGNAME and not having to know the hash for a tag. This scheme will
download a tarball that has a different checksum than before due to a changed
directory name for extraction.
The following MASTER_SITES are provided to retain the old checksum and
directory structure (that require GH_COMMIT):
GH -> GHL
GITHUB -> GITHUB_LEGACY
Differential Revision: https://reviews.freebsd.org/D748
Submitted by: amdmi3
Reviewed by: mat, swills, antoine, bdrewery
With hat: portmgr
New port: java/sigar
The Sigar API provides a portable interface for gathering system information
such as:
* System memory, swap, cpu, load average, uptime, loginsi
* Per-process memory, cpu, credential info, state, arguments, environment,
open files
* File system detection and metrics
* Network interface detection, configuration info and metrics
* TCP and UDP connection tables
* Network route table
This information is available in most operating systems, but each OS has their
own way(s) providing it. SIGAR provides developers with one API to access this
information regardless of the underlying platform. The core API is implemented
in pure C with bindings currently implemented for Java, Perl, Ruby, Python,
Erlang, PHP and C#. This port provides the Java bindings.
WWW: https://support.hyperic.com/display/SIGAR/Home
