Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix build with Boost 1.77 (missing include) #6849

Closed
wants to merge 1 commit into from
Closed

Fix build with Boost 1.77 (missing include) #6849

wants to merge 1 commit into from

Conversation

thesamesam
Copy link

We're relying on boost::geometry so we need to include the "main"
header for it.

Fixes errors like:
error: ‘boost::geometry::strategy::disjoint’ has not been declared

Bug: https://bugs.gentoo.org/808771

We're relying on boost::geometry so we need to include the "main"
header for it.

Fixes errors like:
error: ‘boost::geometry::strategy::disjoint’ has not been declared

Bug: https://bugs.gentoo.org/808771
@thesamesam
Copy link
Author

Actually, I need to check if this is really a problem elsewhere first.

@thesamesam thesamesam closed this Aug 29, 2021
@kk6mrp
Copy link

kk6mrp commented May 12, 2022

What did you end up finding? This PR fixes build issues in Alpine Linux.
https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/33890

@thesamesam
Copy link
Author

thesamesam commented May 12, 2022

What did you end up finding? This PR fixes build issues in Alpine Linux. gitlab.alpinelinux.org/alpine/aports/-/merge_requests/33890

Boost was broken internally (which you seem to have spotted). Your options are to apply the patches or upgrade Boost. Of course, you can apply this patch, but there'll be other stuff which ends up breaking even when it's including things which ought to work.

My recollection is that for this bug, the patch really shouldn't have been needed, and it was just papering over the internal Boost issue (which then got fixed).

(I don't love patching Boost either, but IMO it is what it is, and regressions happen. It's just a consequence of how Boost is laid out and organised.)

@thesamesam thesamesam deleted the boost-1.77 branch May 12, 2022 20:33
@kk6mrp
Copy link

kk6mrp commented May 13, 2022

The author of the PR for the Alpine package tried the patches referenced in the Gentoo issue without any luck. I don't know if we got all of them or not though. We'll probably just need to upgrade boost for it to work.

@thesamesam
Copy link
Author

thesamesam commented May 13, 2022

The author of the PR for the Alpine package tried the patches referenced in the Gentoo issue without any luck. I don't know if we got all of them or not though. We'll probably just need to upgrade boost for it to work.

Honestly, I'd do that -- Boost 1.77 was not a vintage release.

But if you do want to try, it looks like you got the math patch, but not the geometry one (which was so large we had to download it): https://dev.gentoo.org/~sam/distfiles/dev-libs/boost/boost-1.77.0-patches-1.tar.xz.

IIRC Boost 1.78 was much better & rather uneventful and we only had to throw in one additional patch to fix musl: https://gitweb.gentoo.org/repo/gentoo.git/tree/dev-libs/boost/files/boost-1.78.0-interprocess-musl-include.patch.

And within that: you want boost-1.77-geometry.patch, which is just these two patches concatenated:
https://github.com/boostorg/geometry/commit/5110ec7daea0fef72ebdbd41c7f3392502c55945.patch
https://github.com/boostorg/geometry/commit/3dbd2247b63613f68ed4feebb5f5ba390d021b39.patch

@nekopsykose
Copy link

@thesamesam would you mind opening an mr in alpine against main/boost adding the required patches to fix 1.77? i can't seem to understand the full list of the ones you say specifically are needed (unless it's just boost-1.77-geometry.patch + boost-1.77-math-deprecated-include.patch from the patches tarball)

@nekopsykose
Copy link

nekopsykose commented May 13, 2022

(and if it is just those, then it's https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/34353 , but it would help me if you can confirm :) )

@kk6mrp
Copy link

kk6mrp commented May 13, 2022

@nekopsykose Yes, those are the only ones he was referring to.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants