| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
| |
Approved by: portmgr (for Mk/bsd.port.mk part)
Tested by: Multiple -exp runs
|
|
|
|
| |
starting with D
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
|
| |
PR: ports/121691
Submitted by: Scot Hetzel <swhetzel@gmail.com>
|
|
|
|
|
| |
PR: ports/116639
Submitted by: aDe
|
|
CUnit is a lightweight system for writing, administering,
and running unit tests in C. It provides C programmers a
basic testing functionality with a flexible variety of user
interfaces. CUnit is built as a static library which is
linked with the user's testing code. It uses a simple
framework for building test structures, and provides a rich
set of assertions for testing common data types. In addition,
several different interfaces are provided for running tests
and reporting results.
WWW: http://cunit.sourceforge.net/
PR: ports/114934
Submitted by: Stefan Pauly <stefan@fh-mainz.de>
|