mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Ladislav Michl <oss-lists@triops.cz>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] pkg-config-wrapper issue
Date: Mon, 3 Oct 2022 22:43:45 +0200	[thread overview]
Message-ID: <YztJge63wmF4prFJ@lenoch> (raw)
In-Reply-To: <BYAPR14MB30787CFC6DF335A2C40F501CF05B9@BYAPR14MB3078.namprd14.prod.outlook.com>

On Mon, Oct 03, 2022 at 06:14:34PM +0000, Richard OGrady wrote:
> Hello,
> 
> We are using ptxdist 2022.07 and are building 2 packages, libimxvpuapi2 and libimxdmabuffer.
> libimxvpuapi2 depends on libimxdmabuffer and accordingly libimxvpuapi2.in selects libimxdmabuffer.

Those 'depends on' and 'select' are actual keywords used in *.in files
or just a description?

> The libimxvpuapi2 build fails during config.  The config file shows
> 
> Checking for 'libimxdmabuffer >= 0.9.0'
> ['/home/rich/imx6_3D104X_fsl6/Grayhill-iMX6/platform-3D50_std/sysroot-cross/bin/pkg-config', '--cflags', '--libs', 'libimxdmabuffer', '>=', '0.9.0']
> err: pkg-config: warning: blocking 'libimxdmabuffer': not selected by 'libimxvpuapi2'
> 
> So pkg-config-wrapper is blocking the libimxdmabuffer package.  The code that does this in pkg-config-wrapper is:
> 
>         for pkg in ${pkgs}; do
>            if [[ ! " ${whitelist} " =~ " ${pkg} " && ! "${pkg}" =~ '-uninstalled' ]]; then
>               echo "$(basename ${0}): warning: blocking '${pkg}': not selected by '${PKGCONFIG_WHITELIST_SRC}'" >&${ERROR_FD}
>               exit 1
>            fi
>        done
> 
> We can get rid of the issue by commenting out the code above in pkg-config-wrapper but it seems that then breaks some other packages.
> Libimxdmabuffer is version 1.1.2.  Both packages are using waf to build.
> 
> What could be going wrong?

It is a bit hard to tell without seeing actutal code, but from description
above I guess you created circular dependency which got dropped.

> Rich OGrady
> 
> 



       reply	other threads:[~2022-10-03 20:44 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BYAPR14MB30787CFC6DF335A2C40F501CF05B9@BYAPR14MB3078.namprd14.prod.outlook.com>
2022-10-03 20:43 ` Ladislav Michl [this message]
2022-10-04 13:57   ` Richard OGrady
     [not found] ` <MN2PR14MB30871631A8122DDEA101C69BF05D9@MN2PR14MB3087.namprd14.prod.outlook.com>
2022-10-07  7:37   ` [ptxdist] pkg-config-wrapper Michael Olbrich
     [not found]     ` <BYAPR14MB307877E0F9AF8D0E8C4D545CF05F9@BYAPR14MB3078.namprd14.prod.outlook.com>
2022-10-07 15:28       ` Michael Olbrich
2022-10-10 14:11         ` Richard OGrady

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=YztJge63wmF4prFJ@lenoch \
    --to=oss-lists@triops.cz \
    --cc=ptxdist@pengutronix.de \
    /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