All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <pvorel@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] uclinux support?
Date: Tue, 13 Nov 2018 09:56:15 +0100	[thread overview]
Message-ID: <20181113085615.GD7182@dell5510> (raw)
In-Reply-To: <20181112142240.GA10234@rei.lan>

Hi,

> > > uClinux support in LTP has been broken for years and nobody seemed to
> > > really care. I even tried to ask if there is someone interesting in
> > > running LTP on uClinux on the uClinux mailing list but it seems that
> > > even the list is basically dead at this point. So for a last year or so
> > > we are slowly getting rid of the uClinux specific bits from the codebase
> > > in order to simplify the LTP maintenance. You are free to step up and
> > > restore uClinux support in LTP if you have time for that but unless that
> > > happens we will continue to stage it out.


> > OK understood, I was right to ask :)

> > I'd like to roll back to a point where it was mostly working, any idea
> > when that would be?

> > I've looked at the history, and tried several commits that seemed to
> > remove uclinux support,
> > but I'm still facing similar errors (I'm now back to 2011....)

> Actually I have no idea. But generally the further back you go the more
> unstable the whole LTP gets. I'm pretty sure you will not be able to
> even compile 10 years old LTP regardless the uClinux enabled or not.

> Looking at the commit logs it looks like last time anything has been
> fixed for uClinux was 2009.

> > A point were a subset worked would be nice, I'd like to run tests
> > involving unwinding and signals.

> You may be better off taking an LTP from 2016 before we added the new
> LTP test library which is about the time we started to remove uClinux
> support, i.e. before commit:

> commit bbdb9f78378c7e038f463efa39d2470e1c51ad54
> Author: Cyril Hrubis <chrubis@suse.cz>
> Date:   Wed Mar 16 15:53:57 2016 +0100

>     lib: Add new test library API

> And disable tests until it compiles.

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
[2] https://buildroot.org/downloads/manual/manual.html#_analyzing_and_fixing_autobuild_failures
[3] http://autobuild.buildroot.net/stats/

  reply	other threads:[~2018-11-13  8:56 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 [this message]
2018-11-13  9:25         ` Christophe Lyon
2018-11-13 14:02           ` Petr Vorel

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=20181113085615.GD7182@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.