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: Wed, 15 Nov 2023 08:04:57 -0700	[thread overview]
Message-ID: <87a5rfnjl2.fsf@tromey.com> (raw)
In-Reply-To: <1d5e5408487d26a90cded2f599cba75ee60c2c6b.camel@linux.ibm.com> (Carl Love's message of "Tue, 14 Nov 2023 14:23:31 -0800")

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

Carl> I have attached the patch, followed by the entire log file.  Hopefully
Carl> you can see something I am missing.  Thanks for the help.

Well, it is definitely a mystery to me.

A pretty normal failure mode is that the compiler emits some warning or
something, and dejagnu thinks this is an error.  This doesn't seem to be
happening in your case.

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

I wonder if this is exiting with a non-zero status.

It's hard to imagine what else it could be.  Like could there be a
message but dejagnu isn't putting it into the log?

What happens if you 'cd' into the appropriate subdir in the source tree
and invoke gnatmake yourself?  I think earlier you said this worked, but
it's good to start with a clean build tree (hence srcdir -- you can 'git
clean .' to nuke the build artifacts)

Tom

  reply	other threads:[~2023-11-15 15:05 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
2023-11-14 22:23       ` Carl Love
2023-11-15 15:04         ` Tom Tromey [this message]
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=87a5rfnjl2.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