ports/sysutils/metalog, branch release/8.0.0FreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=release%2F8.0.02009-08-22T00:35:32Z- Switch SourceForge ports to the new File Release System: categories starting with P,R,S2009-08-22T00:35:32ZDmitry Marakasovamdmi3@FreeBSD.org2009-08-22T00:35:32Zurn:sha1:3eb168f46b2ba49b62efa711ffbdd0a1047a5e5bUpdate CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script.2008-08-21T06:18:49ZRong-En Fanrafan@FreeBSD.org2008-08-21T06:18:49Zurn:sha1:741aa714833b9bb1e9afaaf5124d3f5c60b5e49c
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)
Reset sergei@ due to maintainer-timeouts and no response to email.2008-07-27T04:30:53ZMark Linimonlinimon@FreeBSD.org2008-07-27T04:30:53Zurn:sha1:189bb010c08702d5d887899161ee9c5fe731aabf
Hat: portmgr
- Remove --mandir and --infodir from CONFIGURE_ARGS. They are now default2007-07-24T15:10:14ZRong-En Fanrafan@FreeBSD.org2007-07-24T15:10:14Zurn:sha1:c925c340dd97e7ad1d69c678a1fadd6e4812218d
in bsd.port.mk.
Tested with: my tinderbox on i386 6
Approved by: portmgr
- Update to 0.82007-07-14T15:57:01ZAndrew Pantyukhinsat@FreeBSD.org2007-07-14T15:57:01Zurn:sha1:874fa9c7598cd2a8e64c9c6dc4837b439e577c4d
- Add an rc script
- This update fixes a gcc4 issue
PR: ports/111606 (based on)
Submitted by: araujo
Approved by: sergei (maintainer timeout, since 15 April 2007)
- Add SHA256 checksums to my ports2005-11-25T14:05:38ZSergei Kolobovsergei@FreeBSD.org2005-11-25T14:05:38Zurn:sha1:a66a28cbd38747cf707eb1026f13243db6e619c1- Update to 0.8-rc1 (proper PORTVERSION autogenerated from this DISTVERSION)2005-08-29T12:26:37ZSergei Kolobovsergei@FreeBSD.org2005-08-29T12:26:37Zurn:sha1:9a33838aec3eb1ff7b84430e17c4354c82626144At Kris's request, back out the MACHINE_ARCH spelling correction until2005-04-12T03:26:56ZDavid E. O'Brienobrien@FreeBSD.org2005-04-12T03:26:56Zurn:sha1:c3d8037aeba75366ed06e02fbc981e15b46e7d0a
after 5.4-RELEASE.
Assist getting more ports working on AMD64 by obeying the2005-04-11T08:04:41ZDavid E. O'Brienobrien@FreeBSD.org2005-04-11T08:04:41Zurn:sha1:f2fc2d60ae226a1b8d5411fb4aab91ea92be6f91
Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.
SIZE *DOES* MATTER.2004-01-30T16:03:29ZSergei Kolobovsergei@FreeBSD.org2004-01-30T16:03:29Zurn:sha1:ee6478c3fc0eeb25f42b7cb5b3409376a517a1a4