Re: [yocto] libtool: library search path "/usr/lib" is unsafe for cross-compilation

[Ross Burton]

It's probably because the configure.ac or similar hard-codes a search
in /usr for some libraries and find them there.  This is *entirely* a
bug in the clamav configure.ac and you'll have to inspect it to
determine what library it is looking for, whether it can be turned
off, or whether it should be added as a build dependency in the
recipe.

Ross

On Tue, 11 Aug 2020 at 11:07, Charlie Davies
 wrote:
>
> Hi,
>
> Are there any ideas as to why the issue above is happening?
>
> Thanks,
>
> Charlie 
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50262): https://lists.yoctoproject.org/g/yocto/message/50262
Mute This Topic: https://lists.yoctoproject.org/mt/75955870/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Project Status WW32'20

[Stephen Jolley]

Current Dev Position: YP 3.2 M3

Next Deadline: YP 3.2 M3 build date 2020/8/31

 

Next Team Meetings:

*   Bug Triage meeting Thursday  Aug. 13th at 7:30am PDT (
 https://zoom.us/j/454367603)
*   Monthly Project Meeting Tuesday Sept. 1st at 8am PDT (
 https://zoom.us/j/990892712)
*   Weekly Engineering Sync Tuesday  Aug. 11th at 8am PDT (
 https://zoom.us/j/990892712)
*   Twitch -  See https://www.twitch.tv/theyoctojester

 

Key Status/Updates:

*   YP 3.2 M2 is out of QA and going through release approval
*   We're now in M3 which is the last milestone for new feature
development for this release
*   YP 3.0.4 is due to be built this week and will be the last point
release for zeus as we migrate over to our new LTS policy and cadence.
*   A number of new intermittent autobuilder failures were seen this
week and logged in bugzilla including one showing signs of another bitbake
lockfile race issue.
*   You can see the rest of the list of failures we're continuing to see
by searching for the "AB-INT" tag in bugzilla:

https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT

Help with any of these would be much appreciated, unfortunately it is
proving hard to find anyone interested in helping figure these out and they
significantly hamper our testing.

*   One way to help the project is to help us with bugs that are
currently unassigned but ideally needed during YP 3.2. See:

https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.2_Unassigned_Enhan
cements.2FBugs
*   Help with any of the recent failed AUH recipe upgrades would also be
appreciated.

 

YP 3.2 Milestone Dates:

*   YP 3.2 M2 should release soon.
*   YP 3.2 M3 build date 2020/8/31
*   YP 3.2 M3 Release date 2020/9/11
*   YP 3.2 M4 build date 2020/10/5
*   YP 3.2 M4 Release date 2020/10/30

 

Planned upcoming dot releases:

*   YP 3.0.4 build date 2020/8/10
*   YP 3.0.4 release date 2020/8/21
*   YP 3.1.3 build date 2020/9/14
*   YP 3.1.3 release date 2020/9/25

 

Tracking Metrics:

*   WDD 2404 (last week 2402) (

https://wiki.yoctoproject.org/charts/combo.html)
*   Poky Patch Metrics  

*   Total patches found: 1280 (last week 1271)
*   Patches in the Pending State: 500 (39%) [last week 495 (39%)]

 

The Yocto Project's technical governance is through its Technical Steering
Committee, more information is available at:

 
https://wiki.yoctoproject.org/wiki/TSC

 

The Status reports are now stored on the wiki at:

https://wiki.yoctoproject.org/wiki/Weekly_Status

 

[If anyone has suggestions for other information you'd like to see on this
weekly status update, let us know!]

 

Thanks,

 

Stephen K. Jolley

Yocto Project Program Manager

*Cell:(208) 244-4460

* Email:  sjolley.yp...@gmail.com
 

 

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50263): https://lists.yoctoproject.org/g/yocto/message/50263
Mute This Topic: https://lists.yoctoproject.org/mt/76127522/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] cmake-based project with system lib dependency

[Sergey Ivanov]

Hi there.
I want to configure the cmake-based project with dependency on library
libuuid.
The latter is located under util-linux and populated in my
build/tmp/deploy/images/qemuarm/core-image-minimal-dev-qemuarm.manifest:

util-linux-dev armv7vet2hf_neon 2.35.1 (here should be header as well and
static library)
...
util-linux-uuidd armv7vet2hf_neon 2.35.1 (i believe the only library)
...
My bb file is:

SUMMARY = "Recipe to build the 'helloworld-cpp-direct-compile' in cpp"
SECTION = "common_templates"

SRC_URI = "file://CMakeLists.txt \
   file://foo.cpp \
   file://foo.h "

inherit pkgconfig cmake

S = "${WORKDIR}"
OECMAKE_GENERATOR = "Unix Makefiles"
# project version seems to not be propagated properly
EXTRA_OECMAKE="-DCMAKE_PROJECT_VERSION=${PV}"


while my CMake file has:

pkg_check_modules(uuid REQUIRED IMPORTED_TARGET "uuid >= 2.25")


Now I obtain the error from cmake:
-- Checking for module 'uuid >= 2.25'
--   No package 'uuid' found
CMake Error at
recipe-sysroot-native/usr/share/cmake-3.16/Modules/FindPkgConfig.cmake:467

What philosophy of yocto to make it work? In other words where 'stage' is
supposed to be located so pkgconfig will find library?

-- 
Kind regards,
Sergey Ivanov
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50264): https://lists.yoctoproject.org/g/yocto/message/50264
Mute This Topic: https://lists.yoctoproject.org/mt/76131485/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

[yocto] Yocto Technical Team Minutes, Engineering Sync, for August 11 2020

[Trevor Woerner]

Yocto Technical Team Minutes, Engineering Sync, for August 11 2020
archive: 
https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit

== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.

== attendees ==
Trevor Woerner, Stephen Jolley, Armin Kuster, Bruce Ashfield, Jan-Simon
Möller, Tim Orling, Jeremey Puhlmann, Paul Barker, Mark Morton, Alejandro
H, Randy MacLeod, Michael Halstead, Richard Purdie, Trevor Gamblin,
(callin), Ross Burton, Peter Kjellerstedt, Steve Sakoman

== notes ==
- 3.2-M2 out of QA, in final release process, looks good
- now in 3.2-M3, last milestone for features
- 3.2-M4, in september, only for bug fixes
- 3.0.4 (last Zeus) should be built and out this week (if all goes well),
  this is the “stutter step”, then we go to 6 months
- some more AB failures added to the list
- some 3.2 bugs that don’t have owners

== general ==
RP: some “old” AB failures have reappeared, perhaps a lock file issue in
bitbake
RP: there is a package data one that might be debuggable and reproducible

RP: relatively quiet week, a couple bitbake patches (, colourizing
output)

MarkM: what’s the next step for sphinx?
RP: a list was made of the areas to work on (from Nico), we just need people
to sign up
RP: the one I’m going to look at is how to get the versioning to work on the
website

PaulB: meta-kernel layer, seems to be some issues with naming
Ross: we have been using meta-kernel, i can see an argument to rename to
meta-mainline-kernel, perhaps, since meta-kernel is a bit generic
RP: my concern is that meta-kernel doesn’t convey what it does
PaulB: my intention was to make it a common place for common kernels (e.g.
Linaro kernel can be used on a bunch of ARM boards). also my hope was to
support back to kernels that aren’t “current” (e.g. 4.4). so it’s
not just a “mainline” layer
RP: i believe there’s a way to get the mainline kernel with linux-yocto
PaulB: i need to be able to flick customers between, e.g. a 4.4 and a mainline
quickly
TrevorW: the magic to get mainline with linux-yocto is to set
PREFERRED_PROVIDER to linux-yocto-dev
RP: it’s a tricky situation, Bruce does a lot of work, sometimes work that
doesn’t show up on the mailing list, I think collaborating with him
would be a good approach. linux-yocto was created to reduce fragmentation.
sometimes understanding linux-yocto can be tricky.
PaulB: maybe just carrying any differences that we need relative to
linux-yocto might be better. some of my customers just want a raw mainline
(with no other patches) since they also support e.g. Debian
Timo: one of the things i do over and over is explaining linux-yocto to people
and how to use it
TrevorW: it was my intent to explain scc files and kernel patches with the
last talk i gave at devday, if there are suggestions please let me know.
hopefully those videos get published
Armin: one can use kernel branch overrides to use the v5.4/base (of
linux-yocto.git)
RP: maybe we need more docs or information
PaulB: meta-kernel was meant to be lightweight, it doesn’t get as much
testing as linux-yocto, it wasn’t meant to step on anyone’s toes
Timo: maybe this is an opportunity to take a look at the kernel development
manual and make sure it is up to date
RP: maybe we could put a barebones kernel mainline recipe for the versions
that are in each release (i’m not saying that’s a good idea, i’m
just throwing out ideas), or maybe add more testing on AB for the
variations of kernels that area already in each release (e.g. the -rt
kernel)
PaulB: this all sounds good
TrevorW: a suggestion: rename recipes-kernel/linux to
recipes-kernel/linux-yocto and then create a recipes-kernel/linux-mainline
for PaulB’s work?
RP: that would only make sense under the assumption that this would be merged
in oe-core
PaulB: we’re a ways off from that conversation, if ever
PaulB: i don’t think this is something that’s going to get resolved for
M3, but maybe sometime after
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#50265): https://lists.yoctoproject.org/g/yocto/message/50265
Mute This Topic: https://lists.yoctoproject.org/mt/76135837/21656
Group Owner: yocto+ow...@lists.yoctoproject.org
Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub  
[arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-