Bug 812728
Summary: | boost_thread does not work with gcc 4.7 | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Braden McDaniel <braden> |
Component: | boost | Assignee: | Petr Machata <pmachata> |
Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 17 | CC: | denis.arnaud_fedora, mnewsome, pertusus, pmachata, pwouters, renich, thibault.north |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2013-02-04 06:43:26 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 754865, 760610 |
Description
Braden McDaniel
2012-04-16 06:00:38 UTC
This appears to have an upstream fix: https://svn.boost.org/trac/boost/ticket/6165 In the absence of an upgrade to 1.49.0, it would be nice to backport this. We already carry that patch. Something else must be broken. I'll look inside. Nevermind. I had a version of Boost installed in my home directory that I'd completely forgotten about. (Closer inspection of the output I pasted suggests as much.) I'm not seeing the problem with the current version of Fedora 17's boost package. Weird. because I just ran into this on F17 with boost-1.48.0-13 Same on Fedora 18. I will reopen the bug. You might be seeing the same error message; however, it is either for completely different reasons than led to this report, or you're doing something as silly as I was. In the former case, you should file a new report. Any update about that ? The issue is still here on F18, boost 1.50.0. That bug is closed. Could you re-create a bug giving more details, for instance with a minimalist program (C++ source code and Makefile) reproducing the error? Thanks for your answer. I updated the program that was producing this error, and it now works well. Thanks, and sorry for the noise. |