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)
Reset the 99 ports still listed under sylvio@
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)
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)
science/elmer(post,-matc): Use modern fortran, unbreak, undeprecate
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.
Mark deprecated with a deadline of 33 days from today since this is
one of two ports that makes us keep lang/gcc34 (which does not even
support FreeBSD 10 and later) and general infrastructure.
Approved by: portmgr (itetcu, 2013-03-31)
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
(Only the first 15 lines of the commit message are shown above )
* Split bsd.port.mk pre and post includes into 3 pieces instead of 2, to
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]
Reset maintainership: Pedro's dev machine has been stolen :-(
Hoping to see you back soon!
Submitted by: Pedro F. Giffuni <giffunip (at) asme.org> (maintainer)
