ports/lang/gcc45/files/java-patch-hier, branch 10-eolFreeBSD ports treehttps://cgit-dev.freebsd.org/ports/atom?h=10-eol2011-11-23T22:27:34ZRemove lang/gcc45 in favor of lang/gcc46 and later. Nothing in the2011-11-23T22:27:34ZGerald Pfeifergerald@FreeBSD.org2011-11-23T22:27:34Zurn:sha1:d4de1b182bd7811959bb73107b66f9f5e652ab4f
tree uses this version of GCC (GCC 4.5.x) any longer and GCC 4.6 has
been the default for USE_FORTRAN=yes and USE_GCC=4.X+ for a while
and has proven itself. Plus, only GCC 4.6 and GCC 4.7 have been
patched to work with FreeBSD 10.x and later.
Feature safe: yes
Update lang/gcc42 to the 20061014 snapshot of GCC 4.2.0, which appends a2006-10-19T16:43:58ZGerald Pfeifergerald@FreeBSD.org2006-10-19T16:43:58Zurn:sha1:0dbe60dd3dfc24c13c83af5b9dbc0d6d6dfd2230
version number to libdata/pkgconfig/libgcj.pc. Fix packaging on amd64
on the way (enabling Java actually was a noop, except for pkg-plist).
Update lang/gcc41 to the 20061013 snapshot of GCC 4.1.2.
These changes allow us to remove the CONFLICT between lang/gcc41 and
lang/gcc42 when building with Java support (the default on i386).
Approved by: portmgr (erwin)
Update to the 20060624 snapshot of GCC 4.2.0.2006-06-26T17:03:03ZGerald Pfeifergerald@FreeBSD.org2006-06-26T17:03:03Zurn:sha1:3427e44afcb1e170e2ff1223a9b02c9a446fac6d
mf-runtime.h no longer pollutes public filename space, so we can
remove our workaround. Refresh files/java-patch-hier.
Update to the 20050730 snapshot of GCC 4.1.0.2005-08-01T19:02:03ZGerald Pfeifergerald@FreeBSD.org2005-08-01T19:02:03Zurn:sha1:8865a0da8241a58ea17377a682aed6402d35146e
Replace the WITHOUT_LIBJAVA knob by WITHOUT_JAVA which also disables
building the compiler and tools proper and avoids fetching the entire
Java frontend and library tarball.
Remove bogus ${PREFIX}/share/classpath/api directory that libjava adds
these days.
Make the (optional) handling of the Fortran and Java frontends easier
to understand.