On Dec 30, 2013, at 00:21, David Evans <dev...@macports.org> wrote: > On 12/29/13 11:48 PM, Jeremy Huddleston Sequoia wrote: >> I strongly suggest either reverting this or fixing openjade to build with >> clang. As it is, this blocks a decent number of ports from building on >> Mavericks =(. >> >> --Jeremy >> >> On Dec 29, 2013, at 12:34, dev...@macports.org wrote: >> >> > The build of gtk-doc was successful on the Mavericks buildbot after this > change. It was able to successfully activate a previously built openjade.
Oh, I see the problem. I had an opensp which was built with clang and thus using libc++ before it was blacklisted (without a revbump). Thus I have a *correct* opensp on my system which causes openjade to fail to link. The builders have a bad version of opensp which allowed a bad version of openjade to build. I've addressed this by un-blacklisting clang in opensp and revbumping to force everyone to rebuild and aborting in openjade until the blocking issue (not building with clang) is addressed. --Jeremy
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
