| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
| |
Reviewed by: exp8 run on pointyhat
Supported by: miwi
|
| |
|
|
|
|
| |
bump PORTREVISION
|
|
|
|
| |
Reported by: pointyhat
|
|
|
|
|
|
| |
implies lang/gcc44 up from lang/gcc43.
Approved by: portmgr
|
|
|
|
|
|
| |
bumped or updated
Requested by: edwin
|
|
|
|
|
|
| |
PR: ports/133397
Submitted by: Stephen Montgomery-Smith <stephen@missouri.edu> (maintainer)
Approved by: tabthorpe (co-mentor)
|
| |
|
|
|
|
|
|
| |
Mk/bsd.gcc.mk.And for this port, CONFIGURE_ENV was bogus to begin with.
Submitted by: Steven Kreuzer <skreuzer@exit2shell.com>
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
Approved by: thierry (mentor)
|
|
|
|
|
|
| |
gfortran has intrinsic etime and we should use it.
Submitted by: linimon
|
|
|
|
| |
effect with bsd.port.mk 1.586.
|
| |
|
| |
|
|
|
|
|
| |
- Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}.
- Bump PORTREVISION for ports intalling files in ${X11BASE}.
|
|
|
|
| |
with letter o-z
|
|
|
|
|
|
|
| |
* Bump port revision.
* Use gfortran compiled lapack.
Submitted by: kris via pointyhat.
|
|
|
|
| |
- portlint(1)
|
|
|
|
| |
Changelog at <http://geuz.org/getdp/doc/VERSIONS>.
|
|
|
|
| |
Changelog at <http://geuz.org/getdp/doc/VERSIONS>.
|
| |
|
| |
|
| |
|
|
|
|
| |
Obtained from: thierry
|
| |
|
|
|
|
| |
after 5.4-RELEASE.
|
|
|
|
| |
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.
|
|
|
|
|
|
|
|
|
|
|
|
| |
According to Hiroki Sato:
"In teTeX 3.0, pdfetex is used for a DVI output, so the texinfo.tex
always detects the PDF output feature. Although there are several means
to fix this problem, I think disabling such detection should be simple
and enough."
Reported by: kris via pointyhat
Obtained from: hrs
|
| |
|
|
|
|
| |
Reported by: Kris via pointyhat.
|
|
finite elements.
Suggested by: Pedro F. Giffuni.
|