From: "Sethu Madhav" <sethu.m@calixto.co.in>
To: Michael Opdenacker <michael.opdenacker@bootlin.com>
Cc: yocto@lists.yoctoproject.org, Vipin Vijayan <vipin.v@calixto.co.in>
Subject: Re: [yocto] libpcre error on compilation time
Date: Fri, 17 Mar 2023 10:17:03 +0530 [thread overview]
Message-ID: <CAFjAHzHibGhqwnnBXa5A885-46j1BO6-CaniQO-BOjiO7HW-2g@mail.gmail.com> (raw)
In-Reply-To: <2663d424-7a09-8346-d2eb-31e96a096cce@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 1091 bytes --]
Hi,
it is not building with the 8.45 version which is included in the
kirkstone version.
Some error is coming at the do compile stage .
We just added libpcre package from the openembedded core git kirkstone
branch. Is there any dependancy or anything that's is needed to do apart
from that?.
Thankyou
On Thu, 16 Mar, 2023, 19:58 Michael Opdenacker, <
michael.opdenacker@bootlin.com> wrote:
> Hi Sethu
>
>
> Thanks for using Kirkstone. Good choice :)
>
> On 16.03.23 at 14:13, Sethu Madhav wrote:
> > Hi,
> > Iam unable to resolve this error on libpcre, during the bitbake. Iam
> > working on the kirkstone YOCTO version and i tried changing the
> > libpcre package but no luck. Can anyone please help with the issue,
> > Iam attaching the error log along with this email.
>
>
> Could you show us your changes?
> From your logs, we still see the standard libpcre_8.45.bb getting
> build. At least, you didn't change the version number in the recipe file
> name.
>
> Cheers
> Michael.
>
> --
> Michael Opdenacker, Bootlin
> Embedded Linux and Kernel engineering
> https://bootlin.com
>
>
[-- Attachment #2: Type: text/html, Size: 1751 bytes --]
next prev parent reply other threads:[~2023-03-17 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 13:13 libpcre error on compilation time Sethu Madhav
2023-03-16 14:28 ` [yocto] " Michael Opdenacker
2023-03-17 4:47 ` Sethu Madhav [this message]
2023-03-20 14:03 ` Michael Opdenacker
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=CAFjAHzHibGhqwnnBXa5A885-46j1BO6-CaniQO-BOjiO7HW-2g@mail.gmail.com \
--to=sethu.m@calixto.co.in \
--cc=michael.opdenacker@bootlin.com \
--cc=vipin.v@calixto.co.in \
--cc=yocto@lists.yoctoproject.org \
/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 NNTP newsgroup(s).