Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: George France <france@handhelds.org>
To: Michael Elizabeth Chastain <mec@shout.net>, gdb@sources.redhat.com
Cc: clp@iol.unh.edu
Subject: Re: exit status of 'make check'
Date: Sun, 11 Nov 2001 11:30:00 -0000	[thread overview]
Message-ID: <01112208082500.16429@shadowfax.middleearth> (raw)
In-Reply-To: <200111212321.RAA09463@duracef.shout.net>

Hello Michael,

It has been a while since we chatted. I hope you are doing well.

> > When I ever I do a 'make check' on gdb using the  cvs HEAD tree on either
> > the intel or Alpha architecture. It always returnes a non-zero exit code.
> > The testsuites execute and produce a good gdb.log and gdb.sum files.  Has
> > anybody seen this before??
>
> Yes, this is normal.  I just do:
>
>   make check || true

This was not exactly the solution that I was hoping for. :-)  We need to fix 
this problem.  It would be really useful to know if 'make check' did or did 
not have an anomaly.

Any Ideas before I go mucking about?

Best Regards,


--George


  reply	other threads:[~2001-11-22 13:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-11 10:33 Michael Elizabeth Chastain
2001-11-11 11:30 ` George France [this message]
2001-11-11 22:14   ` Daniel Jacobowitz
2001-11-12 15:02     ` George France
2001-11-13  8:47       ` Daniel Jacobowitz
2001-11-13  9:53         ` George France
2001-11-13 10:05           ` Daniel Jacobowitz
2001-11-13 10:26             ` George France
2001-11-25 20:59               ` George France
  -- strict thread matches above, loose matches on Subject: below --
2001-11-13 10:34 Michael Elizabeth Chastain
2001-11-13 12:38 ` George France
2001-11-25 22:21   ` George France
2001-11-25 21:11 ` Michael Elizabeth Chastain
2001-11-10 10:17 George France

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=01112208082500.16429@shadowfax.middleearth \
    --to=france@handhelds.org \
    --cc=clp@iol.unh.edu \
    --cc=gdb@sources.redhat.com \
    --cc=mec@shout.net \
    /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