Re: [macppc, probably ports-gcc] Unbreak devel/double-conversion (was: Re: new: devel/double-conversion)

2019-10-18 Thread Stuart Henderson
On 2019/10/18 01:19, Charlene Wendling wrote: > That's why portcheck(1) yells if COMPILER_LIBCXX is in WANTLIB and > no COMPILER line with at least ports-gcc is set [0]. I added that check mainly to avoid pulling in multiple standard C++ libraries to the same address space (e.g. via library

Re: [macppc, probably ports-gcc] Unbreak devel/double-conversion (was: Re: new: devel/double-conversion)

2019-10-17 Thread Kurt Mosiejczuk
On Fri, Oct 18, 2019 at 01:19:10AM +0200, Charlene Wendling wrote: > > - Drop Compiler, builds fine with all compilers. No C++11 > Yes, but there are platform-specific quirks that ports-gcc handles > gracefully, unlike the old base one ;) > That's why portcheck(1) yells if COMPILER_LIBCXX is in

[macppc, probably ports-gcc] Unbreak devel/double-conversion (was: Re: new: devel/double-conversion)

2019-10-17 Thread Charlene Wendling
Hi, On Fri, 27 Sep 2019 13:52:49 +0200 Rafael Sadowski wrote: [...] > > Please find attached a re-write of your proposal. > > - move to math, devel to full and I see math is a better category. > - Drop do-test, cmake will handle it for use. > - Add WANTLIB > - Drop Compiler, builds fine with