On 06.10.2016 18:46, Iain Sandoe wrote: > >> On 6 Oct 2016, at 17:42, Rainer Orth <r...@cebitec.uni-bielefeld.de> wrote: >> > >>>> Here's what I tested. This requires a boehm-gc version 7.0 or later >>>> (having the >>>> header files in a gc subdirectory). Depending on your available library, >>>> it >>>> only builds the GC enabled library for the default multilib library, and >>>> just >>>> skips over building the non-default multilib variants (assuming that most >>>> people >>>> won't have a libgc for that installed). The --enable-objc-gc option is not >> >> 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? Matthias
