Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Tom Tromey <tromey@adacore.com>
To: Carl Love <cel@linux.ibm.com>
Cc: Tom Tromey <tromey@adacore.com>,  gdb-patches@sourceware.org
Subject: Re: Ada compile with -fvar-tracking
Date: Tue, 14 Nov 2023 15:03:15 -0700	[thread overview]
Message-ID: <87ttpongbg.fsf@tromey.com> (raw)
In-Reply-To: <fa24824130774c07514686efa55dc19bea4779fa.camel@linux.ibm.com> (Carl Love's message of "Tue, 14 Nov 2023 13:17:53 -0800")

>>>>> "Carl" == Carl Love <cel@linux.ibm.com> writes:

Carl> I still get: 

Carl>    compilation failed: gcc -c -I./ -fvar-tracking -I/..../testsuite/gdb.ada/finish-large -g -I- 
Carl>    /..../testsuite/gdb.ada/finish-large/p.adb

Carl> Unfortunately "compilation failed" doesn't tell me much.

Yeah... I don't know what's happening.  This worked for me.

Can you send the relevant text from gdb.log?  Or even the whole thing
(from just that one .exp)?  Maybe there's something in there.

Carl> So, there is something in the environment or ??? that is causing the
Carl> compilation to fail???

Really shouldn't be AFAIK.

Tom

  reply	other threads:[~2023-11-14 22:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14 19:24 Carl Love
2023-11-14 19:40 ` Tom Tromey
2023-11-14 21:17   ` Carl Love
2023-11-14 22:03     ` Tom Tromey [this message]
2023-11-14 22:23       ` Carl Love
2023-11-15 15:04         ` Tom Tromey
2023-11-15 16:42           ` Carl Love
2023-11-15 17:02             ` Tom Tromey
2023-11-15 17:12               ` Carl Love
2023-11-15 17:23                 ` Keith Seitz
2023-11-15 17:29                   ` Carl Love
2023-11-15 22:59                     ` Carl Love
2023-11-16 14:02     ` Luis Machado
2023-11-16 16:11       ` Carl Love
2023-11-16 21:07         ` Tom Tromey

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=87ttpongbg.fsf@tromey.com \
    --to=tromey@adacore.com \
    --cc=cel@linux.ibm.com \
    --cc=gdb-patches@sourceware.org \
    /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