From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Petr Vorel <petr.vorel@gmail.com>, Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v5 1/2] ltp: Update to 20200120
Date: Sat, 29 Feb 2020 13:53:00 +0000 [thread overview]
Message-ID: <c70d9ceacc5b7a557179ff9fc1b05100b7aa4065.camel@linuxfoundation.org> (raw)
In-Reply-To: <da2bffd2ba22435a66a17044f922ab555d7a3ede.camel@linuxfoundation.org>
On Sat, 2020-02-29 at 13:42 +0000, Richard Purdie wrote:
> On Sat, 2020-02-29 at 13:22 +0000, Richard Purdie wrote:
> > On Sat, 2020-02-29 at 07:46 +0100, Petr Vorel wrote:
> > > At least we know, that once we solve this problem, we can remove
> > > 0002-kernel-controllers-Link-with-libfts-explicitly-on-mu.patch
> > >
> > > Please, how to reproduce this build locally? Is it:
> > > . oe-init-build-env
> > > TCLIBC=musl bitbake ltp
> >
> > Yes, that should be enough.
> >
> > > Or do I need to put something into config files conf/local.conf
> > > or conf/bblayers.conf ?
> > >
> > > I need to double check if musl-fts is really built and whether
> > > the
> > > order of
> > > -lfts is correct. But all this has been solved even for static
> > > build
> > > for Buildroot,
> > > so I guess it's some issue related to openembedded.
> > > Unfortunately,
> > > I'm not much
> > > experienced in openembedded (stepped in, because nobody else has
> > > updated LTP
> > > package yet).
> > >
> > > Khem, any idea, what can be wrong?
> >
> > FWIW I'll run a build here and see if I can spot anything but I'm
> > trying to do other things today!
>
> 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...
Grep suggests LIBS is a configure option, not a makefile one. I tried:
diff --git a/meta/recipes-extended/ltp/ltp_20200120.bb b/meta/recipes-extended/ltp/ltp_20200120.bb
index 847f267b0b7..5be9489a756 100644
--- a/meta/recipes-extended/ltp/ltp_20200120.bb
+++ b/meta/recipes-extended/ltp/ltp_20200120.bb
@@ -16,7 +16,8 @@ LIC_FILES_CHKSUM = "\
DEPENDS = "attr libaio libcap acl openssl zip-native"
DEPENDS_append_libc-musl = " fts "
-EXTRA_OEMAKE_append_libc-musl = " LIBC=musl LIBS=-lfts "
+EXTRA_OEMAKE_append_libc-musl = " LIBC=musl "
+EXTRA_OECONF_append_libc-musl = " LIBS=-lfts "
# since ltp contains x86-64 assembler which uses the frame-pointer register,
# set -fomit-frame-pointer x86-64 to handle cases where optimisation
and this does seem to build for musl. Might be worth runtime testing
that on the autobuilder?
Cheers,
Richard
next prev parent reply other threads:[~2020-02-29 13:53 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 [this message]
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
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=c70d9ceacc5b7a557179ff9fc1b05100b7aa4065.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=petr.vorel@gmail.com \
--cc=raj.khem@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.