public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
	Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Testers with real m68k hardware needed
Date: Thu, 11 May 2017 18:31:36 +0200	[thread overview]
Message-ID: <02c664a6-99ff-fb6c-2b82-e6f7c8b0ee83@vivier.eu> (raw)
In-Reply-To: <e860e027-11ca-e590-59bb-40134fdedd2a@physik.fu-berlin.de>

Le 10/05/2017 à 23:08, John Paul Adrian Glaubitz a écrit :
> 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
> After hours:

...
  CC       test_urcu_defer.o
/tmp/cczwtyzj.s: Assembler messages:
/tmp/cczwtyzj.s:298: Error: syntax error -- statement `add.l
%d1,nr_writes@TLSLE+4(%a0)' ignored
/tmp/cczwtyzj.s:421: Error: syntax error -- statement `add.l
%d1,nr_writes@TLSLE+4(%a0)' ignored
make[2]: *** [test_urcu_defer.o] Error 1
Makefile:1059: recipe for target 'test_urcu_defer.o' failed
make[2]: Leaving directory '/liburcu/userspace-rcu/tests/benchmark'
Makefile:367: recipe for target 'all-recursive' failed
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory '/liburcu/userspace-rcu/tests'
Makefile:474: recipe for target 'all-recursive' failed
make: *** [all-recursive] Error 1

Laurent

  reply	other threads:[~2017-05-11 16:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 21:08 Testers with real m68k hardware needed John Paul Adrian Glaubitz
2017-05-11 16:31 ` Laurent Vivier [this message]
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=02c664a6-99ff-fb6c-2b82-e6f7c8b0ee83@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=debian-68k@lists.debian.org \
    --cc=glaubitz@physik.fu-berlin.de \
    --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