From: Vyacheslav Yurkov <uvv.mail@gmail.com>
To: Joakim.Tjernlund@infinera.com,
"openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>,
"steve@sakoman.com" <steve@sakoman.com>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [OE-core] nanbield: grpc_1.56.2 fails nativesdk build
Date: Tue, 13 Feb 2024 15:14:06 +0100 [thread overview]
Message-ID: <12d6aaa8-1f7d-4da9-985a-8ebb2a51ebc0@gmail.com> (raw)
In-Reply-To: <5009ff89147eb81e88005c6b6f76d195bf010edb.camel@infinera.com>
Joakim,
I answered you last week on the this topic. Quoting it again:
Could this
https://git.openembedded.org/meta-openembedded/commit/meta-oe/recipes-devtools/protobuf?id=b1deec0de476d8f0a0c6427919f57ee5f681ea0e
fix your failure?
Note, oe-core is a wrong list for this discussion, I changed the CC
accordingly.
Slava
On 13.02.2024 15:08, Joakim Tjernlund via lists.openembedded.org wrote:
> On Fri, 2024-02-09 at 15:09 +0000, Joakim Tjernlund via lists.openembedded.org wrote:
>> Whatever I try I always get:
>>> The imported target "protobuf::protoc" references the file
>>>
>>> "/home/jocke/yocto-xr/build/infn-xr/gmcu/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/1.56.2/recipe-sysroot/opt/infn-xr/1.0/sysroots/x86_64-xrsdk-linux/usr/bin/protoc-23.4.0"
>>>
>>> but this file does not exist. Possible reasons include:
>>>
>>> * The file was deleted, renamed, or moved to another location.
>>>
>>> * An install or uninstall procedure did not complete successfully.
>>>
>>> * The installation package was faulty and contained
>>>
>>> "/home/jocke/yocto-xr/build/infn-xr/gmcu/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/1.56.2/recipe-sysroot/opt/infn-xr/1.0/sysroots/x86_64-xrsdk-linux/usr/lib/cmake/protobuf/protobuf-targets.cmake"
>>>
>>> but not all the files it references.
>> Looking at failing path:
>> s /home/jocke/yocto-xr/build/infn-xr/gmcu/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/1.56.2/recipe-sysroot/opt/infn-xr/1.0/sysroots/x86_64-xrsdk-linux/usr/
>> ./ ../ include/ lib/ share/
>>
>> There in no bin dir at all. In lib there are lots of libs, including libprotobuf-c.so
>> To me it feels like bitbake somehow failed to install required bin/protoc-23.4.0 files
>> but misses the bin files as these are normally not needed when building.
>>
>> or perhaps it is rewriting the passed path? What is passed to cmake is:
>> "/home/jocke/yocto-xr/build/infn-xr/gmcu/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/1.56.2/recipe-sysroot-native/usr/bin/protoc"
>>
>> but bitbake somehow rewrite this to:
>>
>> "/home/jocke/yocto-xr/build/infn-xr/gmcu/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/1.56.2/recipe-sysroot/opt/infn-xr/1.0/sysroots/x86_64-xrsdk-linux/usr/bin/protoc-23.4.0"
>>
>> Notice the change to "recipe-sysroot/opt/infn-xr/1.0/sysroots/x86_64-xrsdk-linux/" in the middle.
>>
>> Joakim
> FYI, this works around the problem:
> cat ./meta-xr/recipes-devtools/grpc/grpc_%.bbappend
> #Hack the nativesdk-grpc, copy protobuf's protoc* from sysroot to ${SDKPATHNATIVE}
> #For some reason nativesdk-grpc will not find it and build fails otherwise.
> #Unclear what the bug is but suspect upstream bug
>
> do_configure:prepend:class-nativesdk () {
> MY_PREFIX="${TOPDIR}/tmp/work/x86_64-nativesdk-xrsdk-linux/nativesdk-grpc/${PV}"
> MY_FROM="/recipe-sysroot-native/usr/bin/"
> MY_TO="/recipe-sysroot/${SDKPATHNATIVE}/usr/bin/"
> mkdir -p "${MY_PREFIX}${MY_TO}" # Create missing DEST dir
> cp -ap "${MY_PREFIX}${MY_FROM}"protoc* "${MY_PREFIX}${MY_TO}"
> }
>
> CCing you Steve should you have missed this report.
>
> Joakim
next prev parent reply other threads:[~2024-02-13 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <17B23A54B6BB5F11.15017@lists.openembedded.org>
2024-02-13 14:08 ` [OE-core] nanbield: grpc_1.56.2 fails nativesdk build Joakim Tjernlund
2024-02-13 14:14 ` Vyacheslav Yurkov [this message]
2024-02-13 14:45 ` Joakim Tjernlund
2024-02-13 15:19 ` Joakim Tjernlund
2024-02-13 18:40 ` Vyacheslav Yurkov
2024-02-14 9:42 ` Joakim Tjernlund
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=12d6aaa8-1f7d-4da9-985a-8ebb2a51ebc0@gmail.com \
--to=uvv.mail@gmail.com \
--cc=Joakim.Tjernlund@infinera.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=openembedded-devel@lists.openembedded.org \
--cc=steve@sakoman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox