| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Port changes:
- the version 1.5.0 now recognizes clang for amd64 so
the patch files/patch-EnginePl_machine.h reduced but
it is still needed for i386 build;
- this version correctly defines NO_MACHINE_REG_FOR_REG_BANK
and adds -fcommon for clang, so CFLAGS reduced too;
- the patch files/patch-Ma2Asm_x86__64__any.c rebuilt for new code,
it is still needed as build fails with an error without the patch:
Fatal Error: Segmentation Violation (bad address: 0x100ec814853)
|
|
|
|
| |
It needs GNU as to build and -fcommon to link.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Update to version 1.4.5 released in 2020.
Make it build and run with Clang 10:
- clang has no register reservation for x86, hence patch-EnginePl_machine.h
and -DNO_MACHINE_REG_FOR_REG_BANK to prevent using missing feature;
- add patch-Ma2Asm_x86__64__any.c fetched from upstream SourceForge
post-release commit dealing with PIC issues;
- disable usage of spinlocks that results in a hang eating all available
CPU cycles; fixed with -DUSE_LOCKS=1 -DUSE_RECURSIVE_LOCKS=1
-DUSE_SPIN_LOCKS=0;
- the software uses bundled dlmalloc dated back 2011 that replaces
functions like calloc() with own implemenations and it's calloc()
sometimes fails to clear allocated memory; this results in SIGSEGV
when its own hash-table implementation dereferences junk that
supposed to be NULL pointer, so it fails to complete build;
fixed with MMAP_CLEARS=0.
PR: 231393
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
2019-08-31 devel/pure-stldict: Depends on expiring devel/llvm35
2019-08-31 lang/dmd1: No longer supported upstream
2019-08-31 lang/gprolog: Abandonware upstream (more than five years), fails in various ways with remotely recent compilers
2019-08-31 math/pure-mpfr: Depends on expiring devel/llvm35
2019-08-31 math/pure-rational: Depends on expiring devel/llvm35
2019-08-31 net/pure-sockets: Depends on expiring devel/llvm35
2019-08-31 textproc/pure-csv: Depends on expiring devel/llvm35
2019-08-31 textproc/pure-xml: Depends on expiring devel/llvm35
2019-08-31 x11-toolkits/pure-tk: Depends on expiring devel/llvm35
2019-08-31 databases/pure-sql3: Depends on expiring devel/llvm35
2019-08-31 devel/pure-readline: Depends on expiring devel/llvm35
2019-08-31 devel/pure-stllib: Depends on expiring devel/llvm35
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| |
|
| |
|
|
|
|
| |
Reported by: pkg-fallout
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
version 1.1.0 (via revision 464079).
|
| |
|
|
|
|
| |
- Various cleanups + regenerate pkg-plist.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(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
|
|
|
|
| |
Reported by: rakuco
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
| |
gplc -c --fast-math fd2c.pl
====>> Killing runaway build after 7200 seconds with no output
PR: 216707
Reported by: antoine (via exp-run)
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
| |
Approved by: portmgr blanket
|
|
|
|
|
|
|
|
| |
<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
|
| |
|
|
|
|
|
| |
I'm not touching ruby19/ruby20/ruby21, but they also check for :MDOCS
without defining it in OPTIONS_DEFINE.
|
|
|
|
|
|
|
|
|
|
| |
- Stage support
- Add LICENSE
- Pet portlint
PR: 191072
Submitted by: Keith Gaughan<k@stereochro.me>
Approved by: maintainer(timeout, >28 days)
|
|
|
|
| |
Approved by: portmgr
|
|
|
|
| |
lang)
|
|
|
|
|
|
|
| |
Point MASTER_SITES to old_versions/, which is where previous releases go.
PR: ports/179656
Submitted by: John Marino <draco@marino.st> (maintainer)
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
PR: ports/165961
Submitted by: maintainer, nsmoot@make.sh
Feature safe: yes
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Approved by: portmgr (for Mk/bsd.port.mk part)
Tested by: Multiple -exp runs
|
|
|
|
|
|
|
|
|
| |
- 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
|
|
|
|
|
|
| |
PR: 141440
Submitted by: Nathan Smoot <putwastehere@gmail.com>
Feature safe: yes
|
|
|
|
|
|
| |
PR: 143232
Submitted by: Hung-Yi Chen <gaod@hychen.org>
Approved by: maintainer timeout
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
Tested by: exp build run (erwin)
|
|
|
|
| |
to run it on a tinderbox, so it stays i386 for now.
|
|
|
|
|
| |
PR: ports/116639
Submitted by: aDe
|
|
|
|
|
| |
PR: ports/100962
Submitted by: Stanislav Sedov
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
| |
Approved by: krion@
|
|
|
|
| |
Currently I do not have the resources to find out why it's breaking
|