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

[package] boost/1.70: bcp segfaults on ubuntu16.04 with namespace and namespace_alias #403

Closed
firewave opened this issue Nov 29, 2019 · 2 comments
Labels
bug Something isn't working

Comments

@firewave
Copy link

Package and Environment Details

  • Package Name/Version: boost/1.70, boost/1.71
  • Operating System+version: Linux Ubuntu 16.04

Steps to reproduce

Configure with boost:namespace = boost_ns and boost:namespace_alias = True and try to build on ubuntu16.04.
This does not happen with Boost 1.69 or on newer ubuntu versions.

Logs

Click to expand log
...
INFO: tracking source dependencies of library log due to presence of "class light_rw_mutex
{" in file "boost/log/detail/light_rw_mutex.hpp"
INFO: tracking source dependencies of library random due to presence of "class random_device : private noncopyable
{" in file "boost/random/random_device.hpp"
CAUTION: don't know how to trace depenencies through macro: "BOOST_SPIRIT_HEADER" in file: libs/spirit/repository/test/test_headers/test.cpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_SPIRIT_HEADER" in file: libs/spirit/repository/test/test_headers/test.cpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_SPIRIT_HEADER" in file: libs/spirit/test/test_headers/test.cpp
CAUTION: don't know how to trace depenencies through macro: "BOOST_SPIRIT_HEADER" in file: libs/spirit/test/test_headers/test.cpp
Segmentation fault (core dumped)

An upstream bug report has been filed - boostorg/bcp#6 - and a patch is available - boostorg/bcp@6dff7a9

@firewave firewave added the bug Something isn't working label Nov 29, 2019
@SSE4
Copy link
Contributor

SSE4 commented Nov 29, 2019

okay, we have to apply the patch for 1.70 and 1.71

@perseoGI
Copy link
Contributor

perseoGI commented Sep 2, 2024

I'm closing this issue as boost recipe has change A LOT since this issue was open.

If this issue remains, do not hesitate to reopen it! 😄

@perseoGI perseoGI closed this as completed Sep 2, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants