Re: [committed] config.gcc: abstract thread_file setting for allrtems targets

[Ralf Corsepius <corsepiu at faw dot uni-ulm dot de>]

On Thu, 2003-09-25 at 09:10, Nathanael Nerode wrote:
> I noted one thing shared by all of the many rtems configurations.
> I abstracted it.  :-)  I checked the logic on this carefully; enable_threads
> and thread_file can't be used or set between the new location and the old
> ones.
> 
> 	* config.gcc: New 'widely ported system' clause for rtems.
> 	Set thread file there, not in individual clauses.
> 
> Index: config.gcc
> ===================================================================
> RCS file: /cvs/gcc/gcc/gcc/config.gcc,v
> retrieving revision 1.378
> diff -u -r1.378 config.gcc
> --- config.gcc	25 Sep 2003 07:00:01 -0000	1.378
> +++ config.gcc	25 Sep 2003 07:04:26 -0000
> @@ -479,6 +479,11 @@
>        ;;
>    esac
>    ;;
> +*-*-rtems*)
> +  case ${enable_threads} in
> +    yes) thread_file='rtems' ;;
> +  esac
> +  ;;

I think, the part above is correct, but ...

>  *-*-vxworks*)
>    tmake_file=t-vxworks
>    tm_file="${tm_file} elfos.h svr4.h vxworks.h"
> @@ -643,9 +648,6 @@
>  arm*-*-rtems*)
>  	tm_file="dbxelf.h elfos.h arm/unknown-elf.h arm/elf.h arm/aout.h arm/arm.h arm/rtems-elf.h rtems.h"
>  	tmake_file="arm/t-arm-elf t-rtems"
> -	if test x$enable_threads = xyes; then
> -	  thread_file='rtems'
> -	fi
>  	use_fixproto=no
             ^^^^^^^^^^^^^^^
... I am hesitant about this.

Though it is true that all official *-rtems* toolchains apply newlib and
therefore should not require fixproto, *-rtems* toolchains basically
aren't necessarily strictly tied to newlib.

To but it into other words: *-*-rtems and *-*-rtems<version> toolchains
(The target tuples used for the official RTEMS toolchains) are newlib
based, but there could be other toolchain versions which are not based
on newlib and might require fixproto.

Ralf