| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
|
|
|
|
|
| |
Reflect the move to Google Code.
Feature safe: yes
|
|
|
|
|
|
| |
to 7.19.2.
Bump PORTREVISION, even on the ports that do not have a versioned
dependency, since the binaries will most probably still stop working.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
|
|
|
|
| |
FreeBSD versions: 5.3 and up, 6.x, 7.x, 8-CURRENT
|
| |
|
|
|
|
|
|
|
|
| |
In addition to the patch from Vasil, also finally remove the warning
about the incompatibility with ancient curlpp versions.
PR: 108295
Submitted by: vd
|
|
|
|
|
|
|
|
|
|
| |
This is a no-op for gcc 3.x.
While I'm here, specify the build target in the way the GNU configure
script wants it.
No PORTREVISION bump, since neither of these changes affects the build
output in any way - well, except for the build actually succeeding with
gcc 4.1 :)
|
|
|
|
|
|
|
|
|
|
| |
Bump PORTREVISION of all dependent ports.
Fix the build errors in the few ports that still use the long deprecated,
and now obsoleted, cURL options.
Thanks to everyone who took the time to look over the patch!
Discussed on: -ports
|
| |
|
| |
|
|
|
|
| |
Approved by: krion@
|
|
|
|
| |
Reported by: fenner's survey
|
|
|
|
|
| |
PR: 84429
Submitted by: Vasil Dimov <vd@datamax.bg>
|
|
|
|
|
|
| |
PR: ports/82108
Submitted by: Vasil Dimov <vd@datamax.bg>
Approved by: maintainer timeout (1 month)
|
|
|
|
| |
Approved by: portmgr
|
| |
|
|
|
|
|
| |
the new gcc in -CURRENT, but also makes a giant leap forward WRT
example programs: they actually run instead of dumping core now!
|
|
|
|
| |
dependent ports.
|
|
|
|
|
|
| |
CURLOPT_PASSWDDATA options which have been deprecated since curl-7.10.8.
Reported by: dosirak via kris
|
|
|
|
|
| |
preparation for fixing some breakage resulting from curl-7.11.1 finally
removing two options marked obsolete for over a year.
|
| |
|
|
|
|
|
|
|
| |
- Support CXXFLAGS properly
PR: ports/62814
Submitted by: Ports Fury
|
| |
|
| |
|
|
A C++ wrapper for libcurl
PR: 59891
|