The Common Data Format (CDF) is a conceptual data abstraction for storing,
manipulating, and accessing multidimensional datasets. The basic component of
CDF is a software programming interface that is a device- independent view of
the CDF data model. The application developer is insulated from the actual
physical file format for reasons of conceptual simplicity, device independence,
and future expandability. CDF files created on any given platform can be
transported to any other platform onto which CDF is ported and used with any
CDF tools or layered applications.
The CDF software, documentation, and user support services are provided by NASA
and available to the public free of charge. There are no license agreements or
costs involved in obtaining or using CDF.
A comparison between CDF, netCDF, HDF and HDF5 is available at
https://cdf.gsfc.nasa.gov/html/FAQ.html
===> The following configuration options are available for cdf3-3.9.2:
DOCS=on: Build and/or install documentation
EXAMPLES=on: Build and/or install examples
===> Use 'make config' to modify these settings
science/cdf: improve and lint port
* Lint and sort Makefile according to portclippy(1)
* Mark as PIE_UNSAFE
* Split post-install stance to respect DOCS and EXAMPLES options
* Strip installed binaries and libs
* Use dynamic SOVERSION via PLIST_SUB
Approved by: yuri@ (Mentor)
Differential Revision: https://reviews.freebsd.org/D52408
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 )
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
Related to revision 499061 bump ports with USES=fortran to have them
benefit from the improved situation where libgcc_s is only used when
absolutely necessary.
Suggested by: tijl
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), part II.
The first part covered 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.
This adds ports with USES=fortran and ports using Mk/bsd.octave.mk
which in turn has USES=fortran.
PR: 214965
Reported by: thierry
Follow-up commit to r396576 since I've forgotten to fix some things:
- Do not patch stuff in `pre-configure' target, do it in `post-patch'
- It is our customary practice to mute ${REINPLACE_CMD} invocations
- Do not (mis)use ${MAKE} when ${MAKE_CMD} should be used instead
- Unbreak the build on PowerPC by using correct Fif_ENTRYPOINT() macro that
does not append double underscore to symbol names in binaries (previously
__FreeBSD__ check was removed from the condition, but __PPC__ was left)
- Rename the patch: not only it used now deprecated `+' as path separator,
the patch name itself was just wrong (inconsistent with the patched file)
- Remove useless PKGMESSAGE assignment, bsd.port.mk does this automatically
- Improve `regression-test' target: add dependency on `build', and get rid
of explicit cd'ing to ${BUILD_WRKSRC} by using -C switch of make(1)
- Fix some minor whitespace bugs and reorder the knobs to make more sense
I've removed BROKEN statement entirely (for all Tier-2 systems) while I've
only tested it on PowerPC: it pulls quite heavy GCC 4.8 for Fortran support
and I didn't want to stress our poor flame too much (This is a really slow,
old machine. Be gentle). Since the bug was indeed PowerPC-specific, it is
probably OK (and worth trying anyway).
Cleanup DIST* variables.
When appropriate:
- Try to use DISTVERSION{SUF,PRE}FIX
- Replace PORTNAME-PORTVERSION by DISTNAME
- Convert MASTER_SITES to use macros
- Other light cleanup
With hat: portmgr
Sponsored by: Absolight
Update the default version of GCC in the Ports Collection from GCC 4.7.4
to GCC 4.8.3.
Part II, Bump PORTREVISIONs.
PR: 192025
Tested by: antoine (-exp runs)
Approved by: portmgr (implicit)
Replace "${OPSYS:tl}" with "freebsd" on 4 ports
The following 4 ports will not build correctly if certain variables
are not defined as "freebsd". Defining them as "${OPSYS:tl}" caused
breakage on DragonFly for various reasons. Harding the variables are
a no-op for FreeBSD but fixes the ports on DragonFly.
* games/ioquake3
* graphics/opendx
* science/cdf
* security/john
approved by: portmgr (bapt)
Convert all :U to :tu and :L to :tl
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
Update the default version of GCC used in the Ports Collection from
GCC 4.6.4 to GCC 4.7.3. This entails updating the lang/gcc port as
well as changing the default in Mk/bsd.default-versions.mk.
Part II, Bump PORTREVISIONs.
PR: 182136
Supported by: Christoph Moench-Tegeder <cmt@burggraben.net> (fixing many ports)
Tested by: bdrewery (two -exp runs)
Convert all USE_FORTRAN=yes to "USES=fortran, USE_GCC=yes". In most cases
USE_GCC=yes has been omitted though.
Remove USE_FORTRAN handling from bsd.port.mk and bsd.gcc.mk.
Minor cleanups in some ports like USE_GMAKE, NOPORTDOCS,...
Exp-run: bdrewery
Approved by: portmgr (bdrewery)
Fix a stage symlink.
There may be still some problems with this port:
/usr/local/bin/definitions.K is referring to
/wrkdirs/usr/ports/science/cdf/work/stage
/usr/local/bin/definitions.B is referring to
/wrkdirs/usr/ports/science/cdf/work/stage
/usr/local/bin/definitions.C is referring to
/wrkdirs/usr/ports/science/cdf/work/stage
Update to libmpc version 1.0.1 which brings the following fixes:
- Switched to automake 1.11.6, see CVE-2012-3386.
- #14669: Fixed extraction of CC from gmp.h.
- Fixed case of intermediate zero real or imaginary part in mpc_fma,
found by hydra with GMP_CHECK_RANDOMIZE=1346362345.
This is on top of the following changes from version 1.0
- Licence change towards LGPLv3+ for the code and GFDLv1.3+ (with no
invariant sections) for the documentation.
- 100% of all lines are covered by tests
- Renamed functions
. mpc_mul_2exp to mpc_mul_2ui
. mpc_div_2exp to mpc_div_2ui
(Only the first 15 lines of the commit message are shown above )
Chase a silent update and make fetchable again.
- our patches to support FreeBSD have been included;
- support of Intel C++ and Fortran compilers for Linux has been added.
Full diff available at
<http://pompo.net/ports/cdf31-dist_060130_060209.diff>.
Reported by: Ion-Mihai Tetcu on #bsdports
Common Data Format (CDF) is a conceptual data abstraction for storing
multi-dimensional data sets. The basic component of CDF is a software
programming interface that is a device independent view of the CDF data
model. The application developer is insulated from the actual physical
file format for reasons of conceptual simplicity, device independence,
and future expandability. CDF files created on any given platform can
be transported to any other platform on to which CDF is ported and used
with any CDF tools or layered applications.
A comparison between CDF, netCDF, HDF and HDF5 is available at
<http://cdf.gsfc.nasa.gov/html/FAQ.html>.
