On 2020-08-17 14:25, Alexander Kanavin wrote:
> You need to add DEPENDS = "libmnl" maybe?
>
> RDEPENDS is needed for runtime things like script interpreters or
> supplementary data; plain library dependencies are build-time.

Tried both: DEPENDS and RDEPENDS.  libmnl.pc does exist in another tree
but not visible to the ipset and not sure what environment var is proper
to bring it into the build for ipset.bb

There is a temp/sysroots-components/... tree that contains the .pc file,
but it's not visible to the ipset.bb recipe.  How do I make it visible
in a way that's not a hack?

tmp/sysroots-components/cortexa9hf-neon/libmnl/usr/lib/pkgconfig/libmnl.pc

is not visible under

${WORKDIR}


> On Mon, 17 Aug 2020 at 19:14, Rob Prowel <rprowel@...> wrote:
>
>> I'm trying to add the ipset utility to my arm build so that I can group
>> IP/ports for use in tc and netfilter.  I was able to update the vendor
>> supplied iptools2 recipe to install tc and iptables, but ipset is a
>> fresh recipe, not included in another existing layer.
>>
>> I'm adding the following in its bb file:
>>
>> # -----------------------------------------------------------------
>> SRC_URI =  "file://ipset-7.6.tar.bz2"
>> SRC_URI[md5sum] = "3a6f5952fd1bcf0eefb9c7c087acbfc9"
>>
>>
>> inherit pkgconfig
>>
>> S = "${WORKDIR}/ipset-7.6"
>>
>> RDEPENDS_${PN} += "libmnl"
>

I'm trying to add the ipset utility to my arm build so that I can group
IP/ports for use in tc and netfilter.  I was able to update the vendor
supplied iptools2 recipe to install tc and iptables, but ipset is a
fresh recipe, not included in another existing layer.

I'm adding the following in its bb file:

# -----------------------------------------------------------------
SRC_URI =  "file://ipset-7.6.tar.bz2"
SRC_URI[md5sum] = "3a6f5952fd1bcf0eefb9c7c087acbfc9"


inherit pkgconfig

S = "${WORKDIR}/ipset-7.6"

RDEPENDS_${PN} += "libmnl"

FILES_${PN} =  ""
# list will be populated once I know what the package wants to install

do_configure(){
         ./configure --prefix=/ --host=arm-linuxeabi
}

do_compile(){
         make DESTDIR=${D}
}

do_install(){
         oe_runmake install DESTDIR=${D}
}

# -----------------------------------------------------------------

problem is that it depends on libmnl (which already exists as a lower
layer recipe), and the ipset configure script barfs on pkg-config with
the following message.

| checking whether ln -s works... yes
| checking for libmnl... no
| configure: error: Package requirements (libmnl >= 1) were not met:
|
| No package 'libmnl' found
|
| Consider adjusting the PKG_CONFIG_PATH environment variable if you
| installed software in a non-standard prefix.
|
| Alternatively, you may set the environment variables libmnl_CFLAGS
| and libmnl_LIBS to avoid the need to call pkg-config.
| See the pkg-config man page for more details.
| WARNING: exit code 1 from a shell command.


the PKG_CONFIG_PATH variable seems correct under devshell, but there is
no libmnl.pc file in there.  How do I force libmnl to create and stage a
proper pkg-config .pc file where it needs to be?

Hello All,

Intel and WR YP QA is planning for QA execution for YP build yocto-3.0.3.rc2. We are planning to execute following tests for this cycle:

OEQA-manual tests for following module:
1. OE-Core
2. BSP-hw

Runtime auto test for following platforms:
1. MinnowTurbot 32-bit
2. Coffee Lake
3. NUC 7
4. NUC 6
5. Edgerouter
6. MPC8315e-rdb
7. Beaglebone

ETA for completion is next Wednesday, Aug 19.

Thanks,
Sangeeta

> -----Original Message-----
> From: Poky Build User <pokybuild@...>
> Sent: Saturday, 15 August, 2020 1:06 PM
> To: yocto@...
> Cc: otavio@...; yi.zhao@...; Sangal, Apoorv
> <apoorv.sangal@...>; Yeoh, Ee Peng <ee.peng.yeoh@...>; Chan,
> Aaron Chun Yew <aaron.chun.yew.chan@...>;
> richard.purdie@...; akuster808@...;
> sjolley.yp.pm@...; Jain, Sangeeta <sangeeta.jain@...>
> Subject: QA notification for completed autobuilder build (yocto-3.0.4.rc1)
>
>
> A build flagged for QA (yocto-3.0.4.rc1) was completed on the autobuilder and is
> available at:
>
>
>     https://autobuilder.yocto.io/pub/releases/yocto-3.0.4.rc1
>
>
> Build hash information:
>
> bitbake: fd279f857c98d492f43cc62d9ebae18ce6412b6e
> meta-arm: 38de27d05f104f989adfed5c5363464dd600b316
> meta-gplv2: 0f4eecc000f66d114ad258fa31aed66afa292166
> meta-intel: ce6f8ddd2d7f42a9fe530d30332b0d9695e4904b
> meta-kernel: cb7f0dc5bb1ea0998c8d4fcb486148d4cab575f4
> meta-mingw: 756963cc28ebc163df7d7f4b4ee004c18d3d3260
> oecore: 9cad716656b427e625a470a820b8b29b1ec9f976
> poky: f2eb22a8783f1eecf99bd4042695bab920eed00e
>
>
>
> This is an automated message from the Yocto Project Autobuilder
> Git: git://git.yoctoproject.org/yocto-autobuilder2
> Email: richard.purdie@...
>
>
>

Rename upgradehelper.py into upgrade-helper.py since the conf file and the git
repo are named with a dash to separate "upgrade" and "helper".

The documentation in the README and upgradehelper.py were also already using
upgrade-helper.py instead of upgradehelper.py.

For all those reasons, let's be consistent and rename the python script.

Signed-off-by: Quentin Schulz <foss@...>
---
 - RESEND because I was not subscribed to the ML with this address already,

 upgradehelper.py => upgrade-helper.py | 0
 weeklyjob.sh                          | 2 +-
 2 files changed, 1 insertion(+), 1 deletion(-)
 rename upgradehelper.py => upgrade-helper.py (100%)

diff --git a/upgradehelper.py b/upgrade-helper.py
similarity index 100%
rename from upgradehelper.py
rename to upgrade-helper.py
diff --git a/weeklyjob.sh b/weeklyjob.sh
index 412685e..94598a2 100755
--- a/weeklyjob.sh
+++ b/weeklyjob.sh
@@ -20,7 +20,7 @@ git fetch origin
 git checkout -B tmp-auh-upgrades origin/master

 source $poky_dir/oe-init-build-env $build_dir
-$auh_dir/upgradehelper.py -e all
+$auh_dir/upgrade-helper.py -e all

 # clean up to avoid the disk filling up
 rm -rf $build_dir/tmp/
--
2.26.2