Date: Fri, 03 Oct 2014 13:40:25 -0400 From: Lowell Gilbert <freebsd-ports-local@be-well.ilk.org> To: Manfred Antar <null@pozo.com> Cc: ports@freebsd.org, brion@queeg.com, marino@freebsd.org, cs@freebsd.org Subject: Re: Xtide Broken on X86 X64 current Message-ID: <44vbo1yrue.fsf@be-well.ilk.org> In-Reply-To: <201410030223.s932NVKp010278@pozo.com> (Manfred Antar's message of "Thu, 02 Oct 2014 19:23:31 -0700") References: <201410021826.s92IQ52J017427@pozo.com> <20141002210246.GA10548@spectrum.skysmurf.nl> <201410030223.s932NVKp010278@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Manfred Antar <null@pozo.com> writes: > I've done more research on this. Mac OSX has a patch so this will compile with clang without errors. > This is probably the best for current as clang is default compiler. > This patch from OSX works on 11.0 current Interesting. The patch is basically setting a compiler flag for version of the C++ standard that the file is assumed to meet. Given that I don't need such a patch to build the port with GCC *or* clang on my build machine which is running the latest 10.x, a test build on all of the supported platforms and versions would be a good idea before committing. The port's maintainer will be able to do that. > You have to remove USE_GCC line from Makefile > the patch patches configure.ac > so if you try to make without doing a autoconf in the src dir it will fail > so do make; it will fail; go to xtide src do autoconf; I think the normal syntax to have a port do that is USE_AUTOTOOLS= autoconf > then retry make, it will work. > you could make a patch to the new configure script and it will work fine. > Hope this all make some sense :) It does, but the still should get more testing to make sure it doesn't break other platforms or versions of FreeBSD. Be well.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44vbo1yrue.fsf>