Sylvio's last commit was 17 months ago, a full 5 months after all of his
ports could have been reset per policy. Given the push to complete
staging (48 ports are still unstaged, something like 70+ have already
been staged by other committers) and given that PRs are automatically
assigned but never addressed, it's better just to reset all the ports and
PRs so that it's clear to others that these ports are free to maintain.
Approved by: portmgr (implicit)
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)
These ports are due to be deleted in a couple of days because they use
gcc34. I was curious if they actually specifically needed gcc34 or if
any recent gfortan would do. The answer is these ports build fine with
USES+=fortran, which pulls in lang/gcc rather than the deprecated lang/gcc34.
The elmerpost port was broken on amd64; this is because it needs the -fPIC
flag. I built it successfully in poudriere on FreeBSD 9.2, another platform
that supposed elmerpost can't build on. I did not test i386, we'll see what
QAT says.
The listed maintainer has been unresponsive for months on many ports, so due
to the fact these two ports are scheduled for deletion on Dec 27, I am not
getting prior approval from maintainer. The deprecation and expiration
settings are removed.
one of two ports that makes us keep lang/gcc34 (which does not even
support FreeBSD 10 and later) and general infrastructure and it does
not even build on FreeBSD 9 nor amd64.
Approved by: portmgr (itetcu, 2013-03-31)
- Bump PORTREVISION for all ports depending on libglut since the shlib
version number went from 4 to 3.
- Bump PORTREVISION for all ports depending on libXaw as libXaw.so.8 isn't
installed anymore.
- Couple of ports fixes (mostly missing xorg components added to USE_XORG).
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)
allow OPTIONS to be able to influence dependencies. This is still
experimental [1]
* Teach bsd.gcc.mk about gfortran [2]
* Remove the outdated emulators/linux_base; the new default has been
linux_base-fc4. This will allow the outdated port to be removed [3]
* Add USE_FIREBIRD macros to bsd.database.mk [4]
PR: 93687 [1], 93690 [2], 103184 [3], 103357 [4]
Submitted by: shaun [1], Pedro F. Giffuni <giffunip at asme to org> [2],
gerald [2], thierry [2], vd [3], skv [4]
The function of ElmerPost is to visualize the numerical results produced
by ElmerSolver and other finite element programs. ElmerPost operates with
the data specific to the unknown variables (temperature, velocity,
pressure, displacement etc.) defined in the mathematical model. ElmerPost
plots e.g. contours and vector fields, and can manipulate computed data
into another form using the built-in MATC-language (for instance heat
fluxes from temperature distributions).
Submitted by: Pedro F. Giffuni <giffunip@asme.org>
