All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gyorgy Sarvari <skandigraun@gmail.com>
To: Mathieu Dubois-Briand <mathieu.dubois-briand@bootlin.com>,
	openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH 1/2] boost-build-native: upgrade 1.87 -> 1.89
Date: Mon, 18 Aug 2025 19:38:10 +0200	[thread overview]
Message-ID: <154c9823-5637-4b77-8488-a4f218e68f2c@gmail.com> (raw)
In-Reply-To: <DC5BU6ME8H5L.1TRS1N5LYWRWN@bootlin.com>



On 8/18/25 08:07, Mathieu Dubois-Briand wrote:
> On Sat Aug 16, 2025 at 12:22 PM CEST, Gyorgy Sarvari via lists.openembedded.org wrote:
>> Changelog: https://www.boost.org/releases/1.89.0/
>>
>> Signed-off-by: Gyorgy Sarvari <skandigraun@gmail.com>
>> ---
> Hi Gyorgy,
>
> Thanks for your patch.
>
> It looks like this is breaking the build of kea:
>
> ERROR: kea-2.6.3-r0 do_configure: Execution of '/srv/pokybuild/yocto-worker/qemux86-world-alt/build/build/tmp/work/core2-64-poky-linux/kea/2.6.3/temp/run.do_configure.25537' failed with exit code 1
> ...
> | checking for Boost system library... no
> | configure: error: Linking with -lboost_system -lboost_system is not enough: please make sure libboost_system is installed in an expected location; Check config.log for details, you may be missing other libraries.
>
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/17/builds/2074
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/25/builds/2231
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/6/builds/2253
> https://autobuilder.yoctoproject.org/valkyrie/#/builders/3/builds/2288
>
> Can you fix it please?
>
> Best regards,
> Mathieu
>
>
>

Thanks for the note and the logs - maybe updating boost wasn't a good
idea from me.

Boost has switched the system module to headers-only, which makes kea
unhappy. While kea can also compile with headers only, there is a scary
warning about it causing runtime errors, in general saying it "is NOT
recommended".

kea 3.0 still tries to link with this module. I wanted to submit a bug
upstream, however unfortunately they don't accept gmail addresses for
registration. 

For now I will drop this - but maybe someone else will have better luck.



  reply	other threads:[~2025-08-18 17:38 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-16 10:22 [PATCH 1/2] boost-build-native: upgrade 1.87 -> 1.89 Gyorgy Sarvari
2025-08-16 10:22 ` [PATCH 2/2] boost: upgrade 1.88.0 -> 1.89.0 Gyorgy Sarvari
2025-08-18  6:07 ` [OE-core] [PATCH 1/2] boost-build-native: upgrade 1.87 -> 1.89 Mathieu Dubois-Briand
2025-08-18 17:38   ` Gyorgy Sarvari [this message]
2025-08-19  8:56     ` Alexander Kanavin

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=154c9823-5637-4b77-8488-a4f218e68f2c@gmail.com \
    --to=skandigraun@gmail.com \
    --cc=mathieu.dubois-briand@bootlin.com \
    --cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.