From: Andreas Schwab <schwab@linux-m68k.org>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
Cc: Finn Thain <fthain@telegraphics.com.au>,
Thorsten Glaser <tg@mirbsd.de>,
Debian m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Futex problems with firebird3.0 and openjdk-8 on m68k
Date: Sun, 21 May 2017 09:31:28 +0200 [thread overview]
Message-ID: <m2vaoumzsf.fsf@linux-m68k.org> (raw)
In-Reply-To: <29030655-b6d9-9301-5c0e-fcb78aad28f1@physik.fu-berlin.de> (John Paul Adrian Glaubitz's message of "Sun, 21 May 2017 07:27:43 +0200")
On Mai 21 2017, John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de> wrote:
> 5. cd firebird3.0-3.0.2.32703.ds4/
>
> 6. ./debian/rules binary-arch
>
> It should hang at some point when running the compiled binary on Aranym
> or qemu-system. On qemu-user, it will just crash but for other reasons.
Firebird 3.0.1.32609 built successfully on aranym for me.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2017-05-21 7:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 20:43 Futex problems with firebird3.0 and openjdk-8 on m68k John Paul Adrian Glaubitz
2017-05-10 21:21 ` Thorsten Glaser
2017-05-10 21:58 ` John Paul Adrian Glaubitz
2017-05-11 2:46 ` Finn Thain
2017-05-11 5:55 ` John Paul Adrian Glaubitz
2017-05-11 6:27 ` Finn Thain
2017-05-11 6:38 ` John Paul Adrian Glaubitz
2017-05-11 8:20 ` John Paul Adrian Glaubitz
2017-05-20 6:53 ` Finn Thain
2017-05-21 5:27 ` John Paul Adrian Glaubitz
2017-05-21 7:31 ` Andreas Schwab [this message]
2017-05-21 11:15 ` John Paul Adrian Glaubitz
2017-05-21 12:53 ` John Paul Adrian Glaubitz
2017-05-25 5:17 ` Finn Thain
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=m2vaoumzsf.fsf@linux-m68k.org \
--to=schwab@linux-m68k.org \
--cc=debian-68k@lists.debian.org \
--cc=fthain@telegraphics.com.au \
--cc=glaubitz@physik.fu-berlin.de \
--cc=linux-m68k@vger.kernel.org \
--cc=tg@mirbsd.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.