As seen in PR ada/37681, lack of multilib support in a specific target library can break bootstrap. To avoid this without having to disable multilib support completely, it would be useful to have either a --disable-libada-multilib or (better yet) a generic --disable-multilib[=<liba>,<libb>].
(In reply to Rainer Orth from comment #0) > As seen in PR ada/37681, lack of multilib support in a specific target library > can break bootstrap. To avoid this without having to disable multilib support > completely, it would be useful to have either a --disable-libada-multilib or > (better yet) a generic --disable-multilib[=<liba>,<libb>]. Agreed that the latter option would be better, because even directories that do have multilib support can sometimes have it break on them. Treating libada specially in this regard seems to me like it would just be a half-measure.
This bug has an assignee but its status is still marked as UNCONFIRMED so I'm marking it as ASSIGNED to reflect the fact that it has an assignee.
*** Bug 49582 has been marked as a duplicate of this bug. ***