This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Understanding Multilibs ;-)
Nathanael Nerode <neroden@twcny.rr.com> writes:
|> > Can we do this in such a way to preserve this bit snagged from config-ml.in:
|> > # The build tree is layed out as
|> > #
|> > # ./
|> > # newlib
|> > # m68020/
|> > # newlib
|> > # m68881/
|> > # newlib
|> To be perfectly honest, I don't understand this bit. :-) The layout
|> sounds truly bizarre to me, *and* doesn't seem to correspond to reality.
|>
|> ...Unless the one listed lower down is the 'combo' of m68020 and m68881,
|> and there's no 'just m68881' option, in which case, yes, that's right. :-)
Yes, the m68881 requires at least an m68020, so m68881 alone does not make
sense.
Andreas.
--
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux AG, Deutschherrnstr. 15-19, D-90429 Nürnberg
Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."