Re: sh64 and mulilibs

[amylaar at spamcop dot net (Joern Rennecke)]

> > ../srcw/configure --target=sh64-elf --with-headers --with-newlib --disable-gdb
> 
> No, this doesn't work for me.  I get the -ml multilib and nothing
> else.  How can it work?  t-mlib-sh5-compact, for example, defines:
> 
> ML_sh5_compact=m5-compact/
> 
> but t-sh64 has $(ML_m5_compact:m5_compact=compact) so it will never
> see a set value.

No it hasn't.  Make sure you are looking at version 1.7 .
> 
> Are you sure you don't have any local changes?

The nightly tests are built straight from CVS.  There are only local
patches in the expect and gdb / simulator used.
The build actually builds twelve multilibs, but only three are tested in
order to make the test results come out in a reasonable amount of time.

> > > * How are the C++ test results?
> > 
> > See:
> > 
> > http://gcc.gnu.org/ml/gcc-testresults/2004-09/msg00085.html
> 
> 1) I can't even build newlib because cc1 segfaults in
>    sh_gimplify_va_arg (I sent mail to rth about it).

This sounds like you are using old sources.  This has been a problem when
this function was new.

> 2) Your results don't have any pic/PIC multilibs.  Do they work?

The newlib based bare CPU toolchain generally doesn't use PIC in its
libraries.  Linux uses PIC throughout, and I understand Kaz Kojima builds
sh64-linux-gnu from mainline.  We use a number of local patches
in a 3.2.1 based toolchain to get visibility of symbols in shared
libraries right.