SEGV using -specs on 3.0.1-pre

[Joel Sherrill <joel at OARcorp dot com>]

Hi,

I am trying add support for testing gcc rtems targets.  When you link an 
RTEMS application,
we use the -specs option to augment some of the standard gcc rules in a 
board specific manner.
The usage after install is of this form:

  ${target}-gcc -B${prefix}/${target}/BSP/ -specs bsp_specs -qrtems  
<OTHER OPTIONS>

bsp_specs tend to look about like this :

%rename XXX old_XXX
*XXX:
%{!qrtems: %(old_XXX} %{qrtems: RTEMS WAY FOR THIS BOARD}

With the rename/define new pattern repeated for cpp, lib, startfile, etc.

This works great and gives us a uniform way to link in special 
libraries, define symbols, etc.
with the BSP being in control.

For the 3.0.1 pre-releases, this works well after install.  But the 
-specs alternative
results in the main gcc driver program giving a SEGV.  It appears to 
recurse in
do_specs_1 until it blows the stack. 

Is it not OK to use -specs before install? 

When running the testsuite, xgcc is invoked with a long argument list 
and has the no
standard include and library directories options set.  Is it not OK to 
use -specs
with -nostdlib/-nostdinc? 

Thanks.

-- 
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