If you pass -v to gnatmake, it will output the gcc invocations.
This should be sufficient to find the problem.
Basically, just go to the directory containing c35502i.adb, and
execute the gnatmake command as listed below, with -v added in.
If you only have the 35502i.ada file available, use "gnatchop
35502i.ada"
to get the various units split out in their own files.
You might need to specifically include the "support" directory,
which appears to be /home/rth/work/gcc/bld-sjlj/gcc/testsuite/ada/acats0
from your report.
Hope this helps.
-Geert
On Sep 3, 2009, at 19:00, Richard Henderson wrote:
Can someone tell me how to debug this:
splitting /home/rth/work/gcc/bld-sjlj/gcc/testsuite/ada/acats0/
tests/c3/c35502i.ada into:
c35502i.adb
BUILD c35502i.adb
gnatmake --GCC="/home/rth/work/gcc/bld-sjlj/gcc/xgcc -B/home/rth/
work/gcc/bld-sjlj/gcc/" -gnatws -O2 -I/home/rth/work/gcc/bld-sjlj/
gcc/testsuite/ada/acats0/support c35502i.adb -largs --GCC="/home/
rth/work/gcc/bld-sjlj/gcc/xgcc -B/home/rth/work/gcc/bld-sjlj/gcc/"
/home/rth/work/gcc/bld-sjlj/gcc/xgcc -c -B/home/rth/work/gcc/bld-
sjlj/gcc/ -gnatws -O2 -I/home/rth/work/gcc/bld-sjlj/gcc/testsuite/
ada/acats0/support c35502i.adb
gnatbind -I/home/rth/work/gcc/bld-sjlj/gcc/testsuite/ada/acats0/
support -x c35502i.ali
gnatlink c35502i.ali --GCC=/home/rth/work/gcc/bld-sjlj/gcc/xgcc -B/
home/rth/work/gcc/bld-sjlj/gcc/
./c35502i.o: In function `_ada_c35502i':
c35502i.adb:(.text+0x156): undefined reference to `.L47'
collect2: ld returned 1 exit status
gnatlink: error when calling /home/rth/work/gcc/bld-sjlj/gcc/xgcc
gnatmake: *** link failed.
FAIL: c35502i
I haven't been able to figure out what command to issue from the
command line to reproduce this. Cut and paste from the dejagnu log
doesn't work, which is more than annoying...
r~
