Punt autoconf267->autoconf2686abd00a86b
Port details
french/med4.0.0_3
Modelisation et Echanges de Donnees
- Maintainer
- thierry@FreeBSD.org
- Packages
- fr-med 4.0.0_3
- Upstream
- Higher version available: 6.0.1
- CPE
- none, CVEs only via VuXML
- WWW
- https://www.salome-platform.org/user-section/about/med
- Links
- cgit · VuXML
Unaddressed (0) · The CVE record lists this version as affected, no VuXML entry names the CVE
None. There is no CVE without a VuXML entry for this version.
VuXML only (0) · listed, port not fixed yet
None.
pkg audit reports nothing for this version.Fixed (0)
No VuXML entries for this package.
Commits (90)
Chase Code_Aster's upgrade and depends on Tcl/Tk 8.5.46dfdd113a
Autotools update. Read ports/UPDATING 20100915 for details. Approved by: portmgr (for Mk/bsd.port.mk part) Tested by: Multiple -exp runs8262a7b51d
Fix plist when NOPORTEXAMPLES is defined. Feature safe: yes7482a6fd87
Upgrade to 2.3.6.2498ef79d7
-Repocopy devel/libtool15 -> libtool22 and libltdl15 -> libltdl22. -Update libtool and libltdl to 2.2.6a. -Remove devel/libtool15 and devel/libltdl15. -Fix ports build with libtool22/libltdl22. -Bump ports that depend on libltdl22 due to shared library version change. -Explain what to do update in the UPDATING. It has been tested with GNOME2, XFCE4, KDE3, KDE4 and other many wm/desktop and applications in the runtime. With help: marcus and kwm Pointyhat-exp: a few times by pav Tested by: pgollucci, "Romain Tartière" <romain@blogreen.org>, and a few MarcusCom CVS users. Also, I might have missed a few. Repocopy by: marcus Approved by: portmgr789d75c728
Fix compilation with gcc-43. Reported by: pointyhat via pav602a05df80
Chase Aster's main tarball. No change.4b333e199e
- Upgrade to 2.3.5; - Use aster's distfiles.d59e6ccc9d
- Respect NOPORTDOCS, NOPORTEXAMPLES - Fix plist Reported by: QATe58f735dda
Update CONFIGURE_ARGS for how we pass CONFIGURE_TARGET to configure script. 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)741aa71483Conversion from (now defunct) autoconf-2.61 to autoconf-2.62 Tested by: exp build run (erwin)771ea13f41
Upgrade to 2.3.4.4f254add14
Upgrade to 2.3.3.550f3c221e
Switch autoconf dependencies from 2.53 or 2.59 to 2.61. PR: ports/116639 Submitted by: aDe48420a5ebd
Now we use USE_FORTRAN=yes to use FORTRAN compiler.2fa992f987
- Welcome X.org 7.2 \o/. - Set X11BASE to ${LOCALBASE} for recent ${OSVERSION}. - Bump PORTREVISION for ports intalling files in ${X11BASE}.d4f0d0048aFix plist: since the gfortran migration, some tests are no more installed. Reported by: pointyhat via pav5aa53af802
forgot to commit. a build fix for gfortran.ade65cb2c5
* Migrate to gfortran. * Bump port revision. * Always use F90.ea8575c1f2
- Upgrade MED to 2.3.1; - Assign better CATEGORIES; - Support gfortran; - Add a regression-test target.7bbc1fc7e6
- s,INSTALLS_SHLIB,USE_LDCONFIG,g - these include dns/ editors/ emulators/ finance/ games/ graphics/ maintained by ports@ PR: ports/101916 Submitted by: Gea-Suan Lin <gslin_AT_gslin dot org>10ddcca177
- Limit INDEX contents to 7-bit ASCII characters for greater compatibility0872d1986a
Remove USE_REINPLACE from all categories starting with Fc8a818ace5
Conversion to a single libtool environment. Approved by: portmgr (kris)8503536d38
- Fix plist [1] - Fix xmdump. Reported by: pointyhat via Kris [1]70668bfbc2
Upgrade to 2.2.3.ee826d2747
- Add SHA2567b8e2758ed
Mass-conversion to the USE_AUTOTOOLS New World Order. The code present in bsd.autotools.mk essentially makes this a no-op given that all the old variables set a USE_AUTOTOOLS_COMPAT variable, which is parsed in exactly the same way as USE_AUTOTOOLS itself. Moreover, USE_AUTOTOOLS has already been extensively tested by the GNOME team -- all GNOME 2.12.x ports use it. Preliminary documentation can be found at: http://people.FreeBSD.org/~ade/autotools.txt which is in the process of being SGMLized before introduction into the Porters Handbook. Light blue touch-paper. Run.54a0b86543
At Kris's request, back out the MACHINE_ARCH spelling correction until after 5.4-RELEASE.c3d8037aeb
Assist getting more ports working on AMD64 by obeying the Ports Collection documentation and use 'ARCH' rather than 'MACHINE_ARCH'.f2fc2d60ae
Upgrade to 2.2.2.9290d9054a
Apply a big libtool patch to allow porters to use the libtool installed by the libtoolX ports instead of the one included with each port. Ports that set USE_LIBTOOL_VER=X will now use the ports version of libtool instead of the included version. To restore previous behavior, use the new macro, USE_INC_LIBTOOL_VER. Both macros accept the same argument: a libtool version. For example, to use the ports version of libtool-1.5, add the following to your Makefile: USE_LIBTOOL_VER= 15 To use the included version of libtool with extra hacks provided by libtool-1.5, add the following to your Makefile: USE_INC_LIBTOOL_VER= 15 With this change, ports that had to add additional libtool hacks to prevent .la files from being installed or to fix certain threading issues can now delete those hacks (after appropriate testing, of course). PR: 63944 Based on work by:eik and marcus Approved by: ade (autotools maintainer) Tested by: kris on pointyhat Bound to be hidden problems: You bet9e5632dd66
Fix pkg-plist and install examples. Noticed on dosirak & bento. Approved by: mat (mentor).a1cbc82d98
Whoa there, boy, that's a mighty big commit y'all have there...
Begin autotools sanitization sequence by requiring ports to explicitly
specify which version of {libtool,autoconf,automake} they need, erasing
the concept of a "system default".
For ports-in-waiting:
USE_LIBTOOL=YES -> USE_LIBTOOL_VER=13
USE_AUTOCONF=YES -> USE_AUTOCONF_VER=213
USE_AUTOMAKE=YES -> USE_AUTOMAKE_VER=14
Ports attempting to use the old style system after June 1st 2004 will be
sorely disappointed.3f651573adChase repomove graphics/hdf* -> science/hdf*11a7fb8caf
Bump PORTREVISION on all ports that depend on gettext to aid with upgrading. (Part 2)053fdb6a6b
SIZEify.0c881ba59c
- www.code-aster.org was reorganized. fix fetching PR: ports/60121 Submitted by: Thierry Thomas <thierry@pompo.net>8a0dc91f63
Add med 2.1.5, modélisation et Échanges de Données. PR: 54761 Submitted by: thierry@pompo.net98ad40ed21