Nikita V. Youshchenko writes:
> Hello
>
> > > 3. I'm having bad time with gcc-3.4 sparc multilib target. Current
> > > debian/rules.conf contains code that changes TARGET_ALIAS from
> > > sparc-linux to sparc64-linux. But this causes unwanted side-effects
> > > (such as attempts to use 'sparc64-linux-as' instead of
> > > 'sparc-linux-as' as assembler; that fails because there is no
> > > 'sparc64-linux-as', so it falls back to 'as'; that also fails because
> > > 'as' is native and can't process sparc assembler. Also, files go to
> > > /usr/sparc64-linux/... instead of /usr/sparc-linux/...) If I comment
> > > out TARGET_ALIAS change, buld fails with
> > > In file included from ../../src/gcc/libgcc2.c:56:
> > > ../../src/gcc/libgcc2.h:81: error: no data type for mode `TI'
> > > ../../src/gcc/libgcc2.h:82: error: no data type for mode `TI'
> > > make[4]: *** [libgcc/64/_muldi3.o] Error 1
> > > Before I go deep into upstream code, I'd love to get some advice from
> > > somebody who has better understanding of what that means and how
> > > things work...
> >
> > I remember having stopped at the very same point and then found out
> > about the configury done as above. CC'ed Clint and Ben.
>
> I think I've found a fix to this.
> See the attachement.
> Adding a single line to gcc/config.gcc makes sparc target to build
> correctly, without having to change it to sparc64.
thanks, please could you check if the testsuite is run for 32 and 64?
Matthias
