Number of commits found: 57

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

Add DEPRECATED again

Bump expiration date and reference PR #231393.

Mark BROKEN: fails to build

Reported by:	pkg-fallout

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

The last years this port, based on an upstream abandoned half a decade
ago, has merely seen patching and prodding by several of us, often when
it got into the way of updates of other parts of the Ports Collection.

This is the case once again with a pending update of GCC to version 8,
where we run into

  gmake[2]: Entering directory
'/wrkdirs/usr/ports/lang/gprolog/work/gprolog-1.4.4/src/Fd2C'
  gplc -c --fast-math fd2c.pl
  =>> Killing runaway build after 7200 seconds with no output

after already workarounds in place for other versions of remotely
recent compilers.  Bite the bullet and mark for deprecation and
removal one-and-a-half months from now

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

Bump PORTREVISIONs of all users of math/mpc that we just updated to
version 1.1.0 (via revision 464079).

- Remove unneeded USE_AUTOTOOLS.
- Various cleanups + regenerate pkg-plist.

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

Don't override existing configure args.

Reported by:	rakuco

Disable machine registers on i386.

Follow debians lead [1] and pass --disable-regs on i386, to fix build with gcc6.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=852008

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

lang/gprolog: Clean up port (fix build with non-default options)

The no-docs and no-examples options weren't correct.  The configuration
value in those causes were no absolute paths as apparently expected, but
relative to STAGEDIR.  Fix by letting them install and use post-install
option targets to remove if necessary.

Do other cleanup such as wrap to 80 (when possible) and use options
framework.  Also remove option-dependent packagename; that isn't
conventional.  Also make configure target generic by platform.

lang/gprolog: pass -O3 to unbreak with gcc5

gplc -c --fast-math fd2c.pl
====>> Killing runaway build after 7200 seconds with no output

PR:		216707
Reported by:	antoine (via exp-run)

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.

Reset maintainer

<nsmoot@make.sh>: host in1-smtp.messagingengine.com[66.111.4.74] said: 550
    5.1.1 <nsmoot@make.sh>: Recipient address rejected: User unknown in local
    recipient table (in reply to RCPT TO command)

Sponsored by:	DK Hostmaster A/S

Add DOCS to OPTIONS_DEFINE to ports that check for PORT_OPTIONS:MDOCS.

I'm not touching ruby19/ruby20/ruby21, but they also check for :MDOCS
without defining it in OPTIONS_DEFINE.

- Update to 1.4.4
- Stage support
- Add LICENSE
- Pet portlint

PR:		191072
Submitted by:	Keith Gaughan<k@stereochro.me>
Approved by:	maintainer(timeout, >28 days)

- Convert gmake,bzip2 to USES

Approved by:	portmgr

Add NO_STAGE all over the place in preparation for the staging support (cat:
lang)

Make the port fetchable again.

Point MASTER_SITES to old_versions/, which is where previous releases go.

PR:		ports/179656
Submitted by:	John Marino <draco@marino.st> (maintainer)

Fix build on HEAD by adding USE_GCC=any (uses global register)

- Update to 1.4.1
- Trim Makefile header

While here:
- Remove indefinite article from COMMENT
- Convert to new options framework

PR:		ports/172180
Submitted by:	wen@
Approved by:	maintainer timeout (25 days)
		makc, avilla (mentors, implicit)
Feature safe:	yes

- Update to 1.4.0 and update maintainer address

PR:     ports/165961
Submitted by:   maintainer, nsmoot@make.sh
Feature safe:   yes

Sync to new bsd.autotools.mk

Punt autoconf267->autoconf268

Autotools update.   Read ports/UPDATING 20100915 for details.

Approved by:    portmgr (for Mk/bsd.port.mk part)
Tested by:      Multiple -exp runs

- Fix plist with NOPORTDOCS/NOPORTEXAMPLES. [1]
- Update MAINTAINER. [2]

PR:             ports/141440 [2]
Submitted by:   Nathan Smoot <n.smoot@gmail.com> [2]
Patch by:       swell.k@gmail.com [1]
Feature safe:   yes

Make it build on amd64, too, by adjusting CONFIGURE_TARGET.

PR:             141440
Submitted by:   Nathan Smoot <putwastehere@gmail.com>
Feature safe:   yes

- Update to 1.3.1

PR:             143232
Submitted by:   Hung-Yi Chen <gaod@hychen.org>
Approved by:    maintainer timeout

Reset vs@FreeBSD.org at his request due to lack of time.

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 )

Conversion from (now defunct) autoconf-2.61 to autoconf-2.62

Tested by:      exp build run (erwin)

Update to 1.3.0. It might also build on amd64 now, but I haven't been able
to run it on a tinderbox, so it stays i386 for now.

Switch autoconf dependencies from 2.53 or 2.59 to 2.61.

PR:             ports/116639
Submitted by:   aDe

Fix permissions and use PORTDOCS

PR:             ports/100962
Submitted by:   Stanislav Sedov

Somehow GCC 3.x generates a gprolog binary which fails immediately on startup.
Fall back to GCC 2.95 and bump PORTREVISION accordingly.
This update also brings back the FD-solver!

Maybe somebody should check what other distros do about this, but e.g. blindly
applying the Debian patch set doesn't fix this error.

Reminded by: Fernando López

Unbreak: Build w/o FD-solver on 6.x+
Currently I do not have the resources to find out why it's breaking

BROKEN on 6.0: Does not build

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.

At Kris's request, back out the MACHINE_ARCH spelling correction until
after 5.4-RELEASE.

Assist getting more ports working on AMD64 by obeying the
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.

Unbreak on 5.x by disabling fast-calls. Notice that you will still see
build errors if you have -march=pentium4 in your CFLAGS

PR:             ports/78794
Submitted by:   Arne Wörner

- Update to CVS snapshot 1.2.18 (tarball from Debian)
- Use PORTDOCS/EXAMPLESDIR
- We still use the pre-built docs from 1.2.16

BROKEN on 5.x: Does not compile

Approved by:    portmgr (self)

- Update MAINTAINER-line of my ports to new @FreeBSD.org address
- Nuke 2x USE_SIZE while here

Approved by: linimon (mentor)

Bump PORTREVISION on all ports that depend on gettext to aid with upgrading.

(Part 2)

- Enable line-edit (works fine on -STABLE & -CURRENT)
- Bump PORTREVISION
- Grab maintainership

PR:             60323
Submitted by:   Volker Stolz <stolz@i2.informatik.rwth-aachen.de>

Per bento logs, this port won't configure except on i386.
Mark it as ignore to warn the unwary.  (There's probably
little reason to mark it as broken since it has no
maintainer.  Any volunteers?)

PR:             57594
Submitted by:   Mark Linimon <linimon@lonesome.com>

- Fix build
- Support CFLAGS properly
- Fix COMMENT format

PR:             53390
Submitted by:   KATO Tsuguru <tkato@prontomail.com>

Reset bouncing maintainer address

BROKEN: Does not build

De-pkg-comment.

Fix problems with two files not correctly upgraded during
upgrade from 1.2.1 to 1.2.16.

PR:             ports/45615
Submitted by:   Douglas Anestad <yotta@anestad.com> (maintainer)

Maintainer update to version 1.2.16

PR:             ports/45381
Submitted by:   Douglas Anestad <yotta@anestad.com> <yotta@anestad.com>

add gprolog   A free Prolog compiler developed by Daniel Diaz    

Number of commits found: 57

7 vulnerabilities affecting 93 ports have been reported in the past 14 days

^* - modified, not new

All vulnerabilities

Last updated:
2019-11-18 18:25:45