> On 6 Oct 2016, at 17:56, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: >
>>>> this assumption may not hold, though: in Solaris 11+ where libgc is >>>> bundled, both 32 and 64-bit libs are present, as always. I'd also claim >>>> that for multilib testing in general, it's bad to test different >>>> multilibs with different configurations, so I'd rather have people doing >>>> multilib testing obtain all variants of libgc. >>> >>> likewise on Darwin, people may well build “fat” libraries, and I also >>> would encourage testing of m32/m64, >> >> so you both prefer to hard-fail if any of the libgc variants needed for the >> multilibs is missing? Maybe force this behaviour with --enable-objc-gc=yes, >> and >> skip those which are not available with -enable-objc-gc=auto? > > I wouldn't hard-fail, but completely disable objc-gc with an appropriate > warning. The Objective-C maintainers may have other preferences, though. that seems a reasonable strategy to me too (disable that capability when the library is not present) - I suspect that most people do not usually build with GC support anyway (but no firm statistics to back the hunch). Iain
