qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Claudio Fontana <cfontana@suse.de>
To: Richard Henderson <richard.henderson@linaro.org>,
	Cornelia Huck <cohuck@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
	"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: assert fails in s390x TCG
Date: Fri, 28 Jul 2023 16:40:43 +0200	[thread overview]
Message-ID: <d6e0b264-d56a-92d0-a663-9ee3339ea14f@suse.de> (raw)
In-Reply-To: <a1004734-5eb1-032a-f597-c77aa32eee03@linaro.org>

On 7/28/23 16:28, Richard Henderson wrote:
> On 7/28/23 07:23, Claudio Fontana wrote:
>>> It is a test environment for building packages, so the guest at the time of the error is running ./configure for the package swig-v4.1.1.tar.gz
>>>
>>> checking build system type... s390x-ibm-linux-gnu^M
>>> checking host system type... s390x-ibm-linux-gnu^M
>>> checking for a BSD-compatible install... /usr/bin/install -c^M
>>> checking whether build environment is sane... [New Thread 0x7ffea3fff6c0 (LWP 116436)]
>>> [New Thread 0x7ffec14e26c0 (LWP 116437)]
>>> [New Thread 0x7ffecf73e6c0 (LWP 116438)]
>>> [New Thread 0x7ffecde2c6c0 (LWP 116439)]
>>> [New Thread 0x7ffec2beb6c0 (LWP 116440)]
>>> yes^M
>>> checking for a thread-safe mkdir -p... /usr/bin/mkdir -p^M
>>> checking for gawk... gawk^M
>>> checking whether make sets $(MAKE)... yes^M
>>> checking whether make supports nested variables... yes^M
>>> checking for s390x-ibm-linux-gnu-gcc... gcc^M
>>> checking whether the C compiler works... **
>>>
>>> So I presume we are in:
>>>
>>> AC_PROG_CC
>>>
>>
>>
>> I am rerunning this over and over, and it seems it always aborts there in the same place.
> 
> You didn't say what the host is, only qemu-system-s390x.
> Am I barking up the wrong tree looking at s390x host?
> 
> 
> r~

sorry, no it is an x86 host in this case, running openSUSE Tumbleweed.





  reply	other threads:[~2023-07-28 15:47 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-21  9:08 assert fails in s390x TCG Claudio Fontana
2023-07-24  8:21 ` Claudio Fontana
2023-07-27 17:41 ` Richard Henderson
2023-07-28 13:29   ` Claudio Fontana
2023-07-28 13:33     ` Richard Henderson
2023-07-28 13:45       ` Claudio Fontana
2023-07-28 14:23         ` Claudio Fontana
2023-07-28 14:28           ` Richard Henderson
2023-07-28 14:40             ` Claudio Fontana [this message]
2023-07-28 14:46               ` Claudio Fontana
2023-07-28 16:05     ` Richard Henderson
2023-07-28 16:43       ` Richard Henderson
2024-06-12 12:41         ` Philippe Mathieu-Daudé
2024-06-12 13:08           ` Claudio Fontana
2024-06-12 14:33             ` Philippe Mathieu-Daudé
2023-07-31 11:31 ` Claudio Fontana
2023-07-31 20:51   ` Claudio Fontana
2023-08-04  9:00 ` Issue with s390 TCG and libc __strstr_arch13 [Was: Re: assert fails in s390x TCG] Claudio Fontana
2023-08-04  9:20   ` Issue with s390 TCG and libc __strstr_arch13 Thomas Huth
2023-08-04  9:58     ` Claudio Fontana
2023-08-04 14:21       ` Ilya Leoshkevich

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=d6e0b264-d56a-92d0-a663-9ee3339ea14f@suse.de \
    --to=cfontana@suse.de \
    --cc=alex.bennee@linaro.org \
    --cc=cohuck@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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;
as well as URLs for NNTP newsgroup(s).