public inbox for openembedded-core@lists.openembedded.org
 help / color / mirror / Atom feed
From: "Kory Maincent" <kory.maincent@bootlin.com>
To: Konrad Weihmann <kweihmann@outlook.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] ltp: fix rpc build error
Date: Thu, 17 Dec 2020 11:25:42 +0100	[thread overview]
Message-ID: <20201217112542.7f5c38f4@kmaincent-XPS-13-7390> (raw)
In-Reply-To: <AM9PR09MB473969D9F9FE59640D07DBEEA8C40@AM9PR09MB4739.eurprd09.prod.outlook.com>

Hello Konrad,

On Thu, 17 Dec 2020 11:03:39 +0100
Konrad Weihmann <kweihmann@outlook.com> wrote:

> On 17.12.20 10:55, Kory Maincent wrote:
> > Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> > ---
> >   meta/recipes-extended/ltp/ltp_20200930.bb | 6 +++---
> >   1 file changed, 3 insertions(+), 3 deletions(-)
> > 
> > diff --git a/meta/recipes-extended/ltp/ltp_20200930.bb
> > b/meta/recipes-extended/ltp/ltp_20200930.bb index 7acf15b360..9b17d68f67
> > 100644 --- a/meta/recipes-extended/ltp/ltp_20200930.bb
> > +++ b/meta/recipes-extended/ltp/ltp_20200930.bb
> > @@ -14,7 +14,7 @@ LIC_FILES_CHKSUM = "\
> >       file://utils/benchmark/kernbench-0.42/COPYING;md5=94d55d512a9ba36caa9b7df079bae19f
> > \ "
> >   
> > -DEPENDS = "attr libaio libcap acl openssl zip-native"
> > +DEPENDS = "attr libaio libcap acl openssl zip-native libtirpc"  
> 
> Can we have that as a PACKAGECONFIG entry, please? otherwise I think it 
> will change the behavior of the existing setups.

I assumed the tirpc was disable because they did not manage to build with
it "# ltp network/rpc test cases ftbfs when libtirpc is found".
But if you prefer I can add it to PACKAGECONFIG.

> Also the dependency has a `PROVIDES = "virtual/librpc"`, so I think 
> depending on virtual/librpc should be the safest way

Ok

> 
> >   DEPENDS_append_libc-musl = " fts "
> >   EXTRA_OEMAKE_append_libc-musl = " LIBC=musl "
> >   EXTRA_OECONF_append_libc-musl = " LIBS=-lfts "
> > @@ -44,12 +44,12 @@ TARGET_CC_ARCH += "${LDFLAGS}"
> >   
> >   export prefix = "/opt/${PN}"
> >   export exec_prefix = "/opt/${PN}"
> > +export libdir = "/usr/lib"
> > +export incdir = "/usr/include"  
> 
> Those should be ${libdir} and ${incdir} if I'm not mistaken

The exporting of ${prefix} change the value of ${libdir} and ${incdir}
therefore I set them up again. If I don't set it, pkgconfig can not find
libtirpc.

> 
> >   
> >   PACKAGECONFIG[numa] = "--with-numa, --without-numa, numactl,"  
> 
> 
> >   EXTRA_AUTORECONF += "-I ${S}/testcases/realtime/m4"
> >   EXTRA_OECONF = " --with-realtime-testsuite --with-open-posix-testsuite "
> > -# ltp network/rpc test cases ftbfs when libtirpc is found
> > -EXTRA_OECONF += " --without-tirpc "  
> 
> Should be part of a PACKAGECONFIG entry, with `--without-tirpc` being 
> the default

Ok,

Köry





  reply	other threads:[~2020-12-17 10:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-17  9:55 [PATCH] ltp: fix rpc build error Kory Maincent
2020-12-17 10:03 ` [OE-core] " Konrad Weihmann
2020-12-17 10:25   ` Kory Maincent [this message]
2020-12-17 10:47     ` Konrad Weihmann
     [not found]     ` <16517B4086903658.9537@lists.openembedded.org>
2020-12-17 10:53       ` Konrad Weihmann

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=20201217112542.7f5c38f4@kmaincent-XPS-13-7390 \
    --to=kory.maincent@bootlin.com \
    --cc=kweihmann@outlook.com \
    --cc=openembedded-core@lists.openembedded.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