Paolo Bonzini <[EMAIL PROTECTED]> writes: > Arnaud Charlet wrote: >>> Yes I volunteer. We're in stage1 so we have some time to sort out >>> reported issues before release. >> >> OK. I'm still concerned that there is no simple fallback for all targets >> that will break, except for --disable-multilib which is too strong since >> it impacts other languages. >> >> I'd be much more confortable with e.g. adding a --disable-mutilibada >> or some such that would basically fall back to the previous state. > > I volunteer to check if there is support for > --enable-multilib=libstdc++-v3,libjava and if not add it. Unfortunately, > --disable-multilib=ada cannot work (because --disable-xxx is the same as > --enable-multilib=no).
But --enable-no-multilib=libada would work, or --disable-multilib-libada. Andreas. -- Andreas Schwab, SuSE Labs, [EMAIL PROTECTED] SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany PGP key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5 "And now for something completely different."
