From: Randy MacLeod <randy.macleod@windriver.com>
To: Micah <micah.d.snyder@gmail.com>,
Patrick Regnouf <patrick.regnouf@gmail.com>
Cc: bzip2-devel@sourceware.org
Subject: Re: Yocto recipe
Date: Tue, 26 Mar 2024 14:34:58 -0400 [thread overview]
Message-ID: <3d5f7805-3022-4bad-9ee8-2941b112616f@windriver.com> (raw)
In-Reply-To: <CAMYg5Y-LUOevLWiCsLR1O8vs+HDP9BQV8nsze9FO_2bKF9pJ3A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1530 bytes --]
On 2024-03-26 11:30 a.m., Micah via Bzip2-devel wrote:
> Hi Patrick,
>
> The bzip2 project maintainers don't provide the yocto recipe. I am unsure
> who makes it.
Hi Patrick,
It's part of openembedded-core:
https://layers.openembedded.org/layerindex/branch/master/recipes/?q=bzip2
Please either submit a bug:
https://bugzilla.yoctoproject.org/
including info about what branch you are working on
and how to reproduce the issue
or
just send a patch to the oe-core list once you have
joined: openembedded-core@lists.openembedded.org
https://www.yoctoproject.org/community/mailing-lists/
https://lists.openembedded.org/g/openembedded-core
UNLESS, it's already fixed:
https://lore.kernel.org/openembedded-core/?q=bzip2%3A.*libbz2
https://git.openembedded.org/openembedded-core/log/?qt=grep&q=bzip2%3A
Thanks,
../Randy
>
> Regards,
> Micah
>
> On Fri, Feb 23, 2024 at 2:15 PM Patrick Regnouf via Bzip2-devel <
> bzip2-devel@sourceware.org> wrote:
>
>> bzip2 yocto recipe does not create libbz2.so.1.0
>>
>> as a result
>>
>>
>> /usr/lib/gcc/aarch64-poky-linux/11.4.0/../../../../aarch64-poky-linux/bin/ld:
>> warning: libbz2.so.1.0, needed by
>>
>> /home/nvidia/.vs/trunk/c1545438-b69f-4060-bbe2-cc55a2c7de59/src/Common/ThirdParty/boost/1.72/gcc_aarch64/lib/libboost_iostreams.so.1.72.0,
>> not found (try using -rpath or -rpath-link)
>>
>> so I had to create a bbapend to create just that link
>>
>> It is obviously an oversight... please correct
>>
>> Thanks
>>
>> /Patrick
>>
--
# Randy MacLeod
# Wind River Linux
prev parent reply other threads:[~2024-03-26 18:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-23 19:12 Patrick Regnouf
2024-03-26 15:30 ` Micah
2024-03-26 18:34 ` Randy MacLeod [this message]
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=3d5f7805-3022-4bad-9ee8-2941b112616f@windriver.com \
--to=randy.macleod@windriver.com \
--cc=bzip2-devel@sourceware.org \
--cc=micah.d.snyder@gmail.com \
--cc=patrick.regnouf@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).