public inbox for gcc-rust@gcc.gnu.org
 help / color / mirror / Atom feed
From: Marc <dkm@kataplop.net>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: gcc-rust@gcc.gnu.org
Subject: Re: Test results for gccrs on Debian unstable ia64
Date: Wed, 02 Jun 2021 15:05:00 +0200	[thread overview]
Message-ID: <87v96wzabn.fsf@arrakis.kataplop.net> (raw)
In-Reply-To: <cdbd61b9-b4eb-622f-4f71-afc0e60a201b@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Wed, 2 Jun 2021 14:47:11 +0200")

John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> writes:

> Hi Marc!
>
> On 6/2/21 2:41 PM, Marc wrote:
>>> # of expected passes            2347
>>> # of unexpected failures        21
>>> # of expected failures          26
>> 
>> Would it be possible to have the corresponding .log file ? Looks like
>> nearly all execution tests are KO (3 out of 4...).
>
> Sure, just found the log file. Didn't know that there was one ;).

Thanks! Looks like something is missing :

./block_expr1.exe: error while loading shared libraries: libunwind.so.7: cannot open shared object file: No such file or directory

Is libunwind installed ? Not sure why your exe needs it, maybe that's a
particularity of ia64?

Marc

  reply	other threads:[~2021-06-02 13:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-02 11:27 John Paul Adrian Glaubitz
2021-06-02 12:41 ` Marc
2021-06-02 12:47   ` John Paul Adrian Glaubitz
2021-06-02 13:05     ` Marc [this message]
2021-06-02 13:08       ` John Paul Adrian Glaubitz
2021-06-02 16:14         ` John Paul Adrian Glaubitz
2021-06-02 16:58           ` Marc
2021-06-02 17:00             ` John Paul Adrian Glaubitz
2021-06-02 17:02               ` Marc
2021-06-02 20:39                 ` John Paul Adrian Glaubitz

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=87v96wzabn.fsf@arrakis.kataplop.net \
    --to=dkm@kataplop.net \
    --cc=gcc-rust@gcc.gnu.org \
    --cc=glaubitz@physik.fu-berlin.de \
    /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).