Re: force a compiler install, or default the port to reduced features?

2016-09-26 Thread Lawrence Velázquez
> On Sep 26, 2016, at 4:11 PM, Ken Cunningham  
> wrote:
> 
> And of course I find out that the preferred variant (a nice MacOSX GUI) 
> doesn't build with the default installation on about the only system I didn't 
> test it on - a vanilla 10.6 system (my 10.6 systems are LibCxxOnOlderSystems 
> now, with clang-3.7). 
> 
> So my choice is to let it use the existing default compiler and build a 
> somewhat impaired but usable command-line only version, or force a compiler 
> install (clang-3.4 works, maybe 3.3, clang 3.7 would be best), and get the 
> really much better racing-stripes GUI version. The compiler would be 
> installed precompiled on a vanilla 10.6 system. (LibCxx... systems already 
> have clang-3.7, and so don't have this problem).
> 
> I'm tempted to force the compiler install, and if so it might as well be to 
> clang-3.7.
> 
> Is this the "MacPorts" way?

The usual approach is to blacklist compilers that *don't* work.

vq
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


force a compiler install, or default the port to reduced features?

2016-09-26 Thread Ken Cunningham
One of the ports I've been working on (hatari, an Atari ST emulator) was 
accepted for inclusion. Thank you! Hope everyone enjoys using it.

And of course I find out that the preferred variant (a nice MacOSX GUI) doesn't 
build with the default installation on about the only system I didn't test it 
on - a vanilla 10.6 system (my 10.6 systems are LibCxxOnOlderSystems now, with 
clang-3.7). 

So my choice is to let it use the existing default compiler and build a 
somewhat impaired but usable command-line only version, or force a compiler 
install (clang-3.4 works, maybe 3.3, clang 3.7 would be best), and get the 
really much better racing-stripes GUI version. The compiler would be installed 
precompiled on a vanilla 10.6 system. (LibCxx... systems already have 
clang-3.7, and so don't have this problem).

I'm tempted to force the compiler install, and if so it might as well be to 
clang-3.7.

Is this the "MacPorts" way?

Thanks,

ken

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev