From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Finn Thain <fthain@telegraphics.com.au>
Cc: 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: Thu, 11 May 2017 08:38:42 +0200 [thread overview]
Message-ID: <97dd75af-d1da-5cb6-ef73-e1f968be3d61@physik.fu-berlin.de> (raw)
In-Reply-To: <alpine.LNX.2.00.1705111610410.23897@nippy.intranet>
On 05/11/2017 08:27 AM, Finn Thain wrote:
> That's promising, but it doesn't eliminate glibc as a potential problem.
> Do we have glibc test suite results?
Well, it's potentially a glibc problem. But I haven't fully ruled out
other packages yet. All I know is that it works with an older chroot
which has glibc-2.19. But it may be related to gcc as well, no idea.
>> And on Aranym, I'm running the same kernel on which it works with an
>> older chroot. And, as I said, when I replace the libjvm.so itself, it
>> works. So, it seems the library is getting somehow miscompiled.
>>
>
> ... and hence my race condition hypothesis. But I'm guessing.
But wouldn't it then show in the old chroot sometimes as well? It never
shows there, just with the recent chroot.
>>> I can run the kernel futex test suite under QEMU once this debootstrap
>>> issue is sorted:
>>>
>>> dpkg: error processing package mac-fdisk (--configure):
>>> subprocess installed post-installation script returned error exit status 2
>>> Errors were encountered while processing:
>>> mac-fdisk
>>> Setting up mac-fdisk (0.1-16+b1) ...
>>
>> I'm not sure why you keep including mac-fdisk in your debbootstrap run,
>
> AFAIK I didn't include it. How would it get included?
It shouldn't. It's not necessary at all. Try bootstrapping with --variant=minimal.
> Here's the command I used:
>
> debootstrap --arch=m68k --foreign --no-check-gpg --include=apt,nano unstable /export/debian-68k http://ftp.de.debian.org/debian-ports
Mmh, it doesn't work at the moment because I uploaded a patched glibc package
to "unreleased" and debootstrap doesn't support that. You need a patched
version of debootstrap to make this work.
> Yep, it's Gentoo. But to be fair, it performed a native debootstrap just
> fine. Next time I'll use the native chroot to debootstrap the m68k one.
Unless Gentoo modified debootstrap in some way, that shouldn't be a problem.
Adrian
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - glaubitz@debian.org
`. `' Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
next prev parent reply other threads:[~2017-05-11 6:38 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 [this message]
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
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=97dd75af-d1da-5cb6-ef73-e1f968be3d61@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=fthain@telegraphics.com.au \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox