From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Debian m68k <debian-68k@lists.debian.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Testers with real m68k hardware needed
Date: Wed, 10 May 2017 23:08:12 +0200 [thread overview]
Message-ID: <e860e027-11ca-e590-59bb-40134fdedd2a@physik.fu-berlin.de> (raw)
Hi!
liburcu is currently missing support m68k. The maintainer of the Debian package
has kindly written a patch which adds m68k support to the library [1]. However,
he was told by upstream that the patch should be tested on real hardware.
So, for anyone currently running Debian/m68k, your help is needed. I do have
various m68k machines with Debian myself, but they are currently offline but
I am planning on bringing them back online in some months.
Thus, in the meantime it would be great if someone else with real hardware
readily available could help.
To test, do the following:
# apt update
# apt install git
# apt build-dep liburcu
# mkdir liburcu
# cd liburcu
# git clone https://github.com/mjeanson/userspace-rcu.git
# cd userspace-rcu/
# git checkout m68k
# ./bootstrap
# ./configure
# make | liburcu-build.log
# make check | tee liburcu-check.log
Then please post both liburcu-build.log and liburcu-check.log to the list.
Thanks,
Adrian
> [1] https://github.com/mjeanson/userspace-rcu/commit/b4aa8c191528081d28b1538f0156b91f6cdd1f25
--
.''`. 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 reply other threads:[~2017-05-10 21:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 21:08 John Paul Adrian Glaubitz [this message]
2017-05-11 16:31 ` Testers with real m68k hardware needed Laurent Vivier
2017-05-11 17:01 ` John Paul Adrian Glaubitz
2017-05-12 7:07 ` Laurent Vivier
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=e860e027-11ca-e590-59bb-40134fdedd2a@physik.fu-berlin.de \
--to=glaubitz@physik.fu-berlin.de \
--cc=debian-68k@lists.debian.org \
--cc=linux-m68k@vger.kernel.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