public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
From: Geert Bosch <bosch@adacore.com>
To: Richard Henderson <rth@redhat.com>
Cc: GCC <gcc@gcc.gnu.org>
Subject: Re: [ada] help debugging acats failure
Date: Fri, 04 Sep 2009 02:24:00 -0000	[thread overview]
Message-ID: <6E084C26-7D32-4AE1-A520-29DE3515EB47@adacore.com> (raw)
In-Reply-To: <4AA04A98.3000900@redhat.com>

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~

  parent reply	other threads:[~2009-09-04  2:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4A9F1A8D.5080501@redhat.com>
2009-09-03 23:00 ` Richard Henderson
2009-09-04  1:34   ` Dave Korn
2009-09-04  2:24   ` Geert Bosch [this message]
2009-09-04  6:44   ` Arnaud Charlet
2009-09-04  9:47   ` Richard Guenther
2009-09-07  1:15     ` Dave Korn
2009-09-04  9:51   ` Eric Botcazou
2009-09-05 16:11     ` Richard Henderson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6E084C26-7D32-4AE1-A520-29DE3515EB47@adacore.com \
    --to=bosch@adacore.com \
    --cc=gcc@gcc.gnu.org \
    --cc=rth@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).