Re: cross target report on gcc 3.1-20020423

[Joel Sherrill <joel dot sherrill at OARcorp dot com>]

"David S. Miller" wrote:
> 
>    From: Joel Sherrill <joel.sherrill@OARcorp.com>
>    Date: Thu, 25 Apr 2002 08:52:02 -0500
> 
>    sparc-elf       - boehm-gc/typd_mlc.c: include/private/gcconfig.h:394:
>                            parse error before -- token
> 
> Fixing this requires some work, and thought.
> 
> The location of the bottom of the stack on Sparc is very very
> OS dependant.  What is the OS for sparc-elf and how could we
> determine the appropriate value of STACKBOTTOM for boehm-gc
> on it?

For sparc-elf and any other *-elf or *-coff target, there
is no OS.  So the question is why is sparc-elf special
and fail in boehm-gc.  And it appears that the answer is
pretty simple.  For some reason, the sparc*-*elf*
and sparc64*-*-elf* targets there do not include the 
variable ${libgcj} in their noconfigdir list but sparclite-elf*
does.  You can see this in this fragment:

  sparc-*-elf*)
    if [ x${is_cross_compiler} != xno ] ; then
           target_configdirs="${target_configdirs} target-libstub
target-cygmon"
    fi
    ;;
  sparc64-*-elf*)
    if [ x${is_cross_compiler} != xno ] ; then
           target_configdirs="${target_configdirs} target-libstub
target-cygmon"
    fi
    ;;
  sparclite-*-*)
    if [ x${is_cross_compiler} != xno ] ; then
           target_configdirs="${target_configdirs} target-bsp
target-libstub tar
get-cygmon"
    fi
    noconfigdirs="$noconfigdirs ${libgcj}"
    ;;              

I am testing a fix for this locally.  Who approves check-ins on
configure.in?
I now have two patches for it.
                        
-- 
Joel Sherrill, Ph.D.             Director of Research & Development
joel@OARcorp.com                 On-Line Applications Research
Ask me about RTEMS: a free RTOS  Huntsville AL 35805
   Support Available             (256) 722-9985