Re: [PATCH] Delete GCJ

> On 6 Oct 2016, at 17:56, Rainer Orth <[email protected]> wrote:
>=20

>>>> 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 cla=
im
>>>> that for multilib testing in general, it's bad to test different
>>>> multilibs with different configurations, so I'd rather have people doi=
ng
>>>> multilib testing obtain all variants of libgc.
>>>=20
>>> likewise on Darwin, people may well build =E2=80=9Cfat=E2=80=9D librari=
es, and I also
>>> would encourage testing of m32/m64,
>>=20
>> 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=
=3Dyes, and
>> skip those which are not available with -enable-objc-gc=3Dauto?
>=20
> 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 th=
e 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