http://gcc.gnu.org/bugzilla/show_bug.cgi?id=55243
Georg-Johann Lay <gjl at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |gjl at gcc dot gnu.org
--- Comment #7 from Georg-Johann Lay <gjl at gcc dot gnu.org> 2012-12-02
23:17:19 UTC ---
(In reply to comment #6)
> The GNAT tools are for the host, they have nothing to do with multilibs. How
> come the s-avr-mlib Makefile rule gets invoked here?
avr-gcc supports around 200 devices. In order to keep the various parts of the
compiler in sync, some files are auto-generated from the device description in
$(srcdir)/config/avr/avr-mcus.def.
$(srcdir)/config/avr/t-avr reads:
...
AVR_MCUS = $(srcdir)/config/avr/avr-mcus.def
...
# MULTILIB_OPTIONS
# MULTILIB_DIRNAMES
# MULTILIB_EXCEPTIONS
# MULTILIB_MATCHES
$(srcdir)/config/avr/t-multilib: s-avr-mlib; @true
s-mlib: $(srcdir)/config/avr/t-multilib
s-avr-mlib: $(srcdir)/config/avr/genmultilib.awk $(AVR_MCUS)
$(AWK) -f $< -v FORMAT=Makefile $< $(AVR_MCUS) > tmp-avr-mlib
$(SHELL) $(srcdir)/../move-if-change \
tmp-avr-mlib $(srcdir)/config/avr/t-multilib
$(STAMP) $@
And in config.gcc there is
tmake_file="avr/t-avr avr/t-multilib"
Thus, the assumption is that AWK, SHELL and STAMP are set correctly and
respective tools are available on the build platform.
