Arch Linux User Repository

This package needs to be "synced" with the boost version in extra/boost, please don't mark this package as outdated by checking the latest version.

Latest version atm: https://github.com/boostorg/build/blob/boost-1.72.0/doc/src/history.adoc

Thank you

This package needs to be "synced" with the boost version in extra/boost, please don't mark this package as outdated by checking the latest version.

Latest version atm: https://github.com/boostorg/build/blob/boost-1.72.0/doc/src/history.adoc

Thank you

I'm not absolutely sure how this boost packages should be split, I think that extra/boost-libs is fine.

I think you are right, extra/boost package contains b2 and bjam, but doesn't contain jam files, so it can be considered as a corrupted package, because b2 executable needs this files to work correctly.

i don't think b2 should be in the boost package if it doesn't ship the .jam-files.

the binaries should be taken out of extras/boost, or it should also contain the .jam-files.

nothing marcs can do about it though.

great asap support, thank you, everything is ok now

rolled back to 4.0.1 to keep consistency with extra/boost

+1

But Boost.Build engine distributed in extra/boost package is at v4.0.1, so you get this warning, which is not good and can lead to hard to catch problems:

warning: mismatched versions of Boost.Build engine and core
warning: Boost.Build engine (b2) is 4.0.1
warning: Boost.Build core (at /usr/share/boost-build/src) is 4.1-git

This versions should match, you can check correct boost build version every time at:

https://github.com/boostorg/build/blob/boost-1.72.0/doc/src/history.adoc

+1

hi marc, can you update this to 1.69? here's the PKGBUILD: https://pastebin.com/raw/tmMknVFN

thanks

Hi marcs, any update on this?
Even though b2 and bjam is shipped with the official boost, there is still a need for `boost-build.jam`. Maybe removing b2,bjam from this package to avoid conflicts, but keep the boost-build.jam et al files?

edit: just read in PKGBUILD that you did that already, can you upgrade to 1.63 to match the official boost?

Thanks

Hi augusto,

The problem is that the boost package now owns both b2 and bjam files, and instead of removing them without notice to the user, I prefer to set boost as a conflict until I figure out what to do.

It is a strange situation because boost-build is listed as an optional dependency on the official boost package, but now makes no sense with b2 bundled with boost.