From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] uclinux support?
Date: Tue, 13 Nov 2018 15:02:09 +0100 [thread overview]
Message-ID: <20181113140209.GA24439@dell5510> (raw)
In-Reply-To: <CAKdteOZ7Zj_qJA+NFCnCOVi4_K_7MfsVrHY9qJ5iRYjD_p3SSg@mail.gmail.com>
Hi,
> > FYI LTP compiles under uclibc-ng. Buildroot distribution (which uses glibc,
> > uclibc-ng and musl) disabled it just for musl [1]. It's tested with their
> > autobuild service [2] and currently no build reports are for latest release [3].
> > IMHO it shouldn't be difficult to support musl as well.
> > [1] https://git.busybox.net/buildroot/tree/package/ltp-testsuite/Config.in
> IIUC, it depends on BR2_USE_MMU, which probably means that it
> runs only on targets with an MMU,
Yep.
> which is not my case.
OK, I didn't consider non-MMU system.
> And the "#fork()" comment seems to indicate that otherwise
> LTP fails to build for lack of fork(), which is precisely what I'm seeing.
> Using a brutal -Dfork=vfork helped me go much further,
> and I was actually able to run some of the tests involving pthreads and signals.
I see some vfork support for uclibc in legacy C API (include/old/test.h),
but no support in new C API (as Cyril mentioned).
Good luck.
Kind regards,
Petr
prev parent reply other threads:[~2018-11-13 14:02 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-11 20:23 [LTP] uclinux support? Christophe Lyon
2018-11-12 11:01 ` Cyril Hrubis
2018-11-12 13:47 ` Christophe Lyon
2018-11-12 14:22 ` Cyril Hrubis
2018-11-13 8:56 ` Petr Vorel
2018-11-13 9:25 ` Christophe Lyon
2018-11-13 14:02 ` Petr Vorel [this message]
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=20181113140209.GA24439@dell5510 \
--to=pvorel@suse.cz \
--cc=ltp@lists.linux.it \
/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.