Created attachment 355784 [details] Ebuild update New upstream release. I've tested the attached ebuild both with and without the binary flag. The patch is not needed for this version.
Comment on attachment 355784 [details] Ebuild update --- mlton-20100608.ebuild 2013-04-27 16:05:24.655101686 +0200 +++ - 2013-08-13 15:53:53.686983132 +0200 @@ -7,8 +7,8 @@ DESCRIPTION="Standard ML optimizing compiler and libraries" BASE_URI="mirror://sourceforge/${PN}" SRC_URI="!binary? ( ${BASE_URI}/${P}.src.tgz ) - binary? ( amd64? ( ${BASE_URI}/${P}-1.amd64-linux.static.tgz ) - x86? ( ${BASE_URI}/${P}-1.x86-linux.static.tgz ) )" + binary? ( amd64? ( ${BASE_URI}/${P}-1.amd64-linux.tgz ) + x86? ( ${BASE_URI}/${P}-1.x86-linux.tgz ) )" HOMEPAGE="http://www.mlton.org" @@ -32,10 +32,6 @@ usr/lib/mlton/mlton-compile )" -# Fix Bug 452558 - dev-lang/mlton-20100608 fails to build, unknown type name '__gmp_const' -# Fixed by upstream: https://github.com/MLton/mlton/commit/a658a1f4a76a01f568116598800f49b80cf8ee1a -PATCHES=("${FILESDIR}/${P}-gmp-const.patch") - src_compile() { if use !binary; then has_version dev-lang/mlton || die "emerge with binary use flag first"
Ref Bug 469626, I tried the patch, and while I was able to fetch these, mlton-20100608-1.amd64-linux.tgz is showing up as not a gzip file. Not sure. I'd like to take a stab at the new version, if it's going to get pushed out.
I created a patch to allow it to bootstrap with the hardened toolchain on amd64, now looking at USE=binary
Bumped, thanks to David Brown, jer and Jason Mours for testing and suggestions.
