From: Khem Raj <raj.khem@gmail.com>
To: Petr Vorel <petr.vorel@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 1/2] ltp: Update to 20200120
Date: Sat, 29 Feb 2020 12:44:40 -0800 [thread overview]
Message-ID: <CAMKF1spkOJfT0Gg4GaKQRUroPQEXtge0B_G6hZaCgL7wsXCC1A@mail.gmail.com> (raw)
In-Reply-To: <20200229184006.GB13422@dell5510>
[-- Attachment #1: Type: text/plain, Size: 907 bytes --]
On Sat, Feb 29, 2020 at 10:40 AM Petr Vorel <petr.vorel@gmail.com> wrote:
> Hi Richard, Khem,
>
> > I was able to confirm that fts is in the recipe sysroot and that the
> > compile step is running "make -j 88 LIBC=musl LIBS=-lfts", i.e. its
> > being passed in to ltp. Beyond that I'm a little out my depth to know
> > how/why its not ending up where it should unfortunately. At least the
> > issue does appear to reproduce though...
> Is there a way to compile only LTP and the necessary build dependencies?
>
> if I run this:
> . oe-init-build-env
> MACHINE=qemuarm TCLIBC=musl bitbake ltp
>
> It takes ages and compiles many things (gnutls, iptables, expat, procps,
> tar, ...).
Yeah first time it will have to build all the dependencies unfortunately
but thereafter it should be incremental
Your command is right to build ltp only for musl
>
>
> Kind regards,
> Petr
>
[-- Attachment #2: Type: text/html, Size: 1433 bytes --]
next prev parent reply other threads:[~2020-02-29 20:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 17:57 [PATCH v5 1/2] ltp: Update to 20200120 Petr Vorel
2020-02-28 17:57 ` [PATCH v5 2/2] ltp: Remove mips related open_posix_testsuite patch Petr Vorel
2020-02-28 23:02 ` [PATCH v5 1/2] ltp: Update to 20200120 Richard Purdie
2020-02-29 6:46 ` Petr Vorel
2020-02-29 13:22 ` Richard Purdie
2020-02-29 13:42 ` Richard Purdie
2020-02-29 13:53 ` Richard Purdie
2020-02-29 15:13 ` Khem Raj
2020-02-29 17:00 ` Petr Vorel
2020-02-29 18:40 ` Petr Vorel
2020-02-29 20:44 ` Khem Raj [this message]
2020-02-29 15:12 ` Khem Raj
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=CAMKF1spkOJfT0Gg4GaKQRUroPQEXtge0B_G6hZaCgL7wsXCC1A@mail.gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=petr.vorel@gmail.com \
/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.