Bug 6853 - boost shows errors after upgrading to GCC-4.7.1
Summary: boost shows errors after upgrading to GCC-4.7.1
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-23 03:09 CEST by Thomas Spuhler
Modified: 2012-08-05 00:35 CEST (History)
0 users

See Also:
Source RPM: boost
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Thomas Spuhler 2012-07-23 03:09:18 CEST 
Description of problem:
I gett this error when compiling libkolabxml. I didn't see this with the previous version a week ago.

Version-Release number of selected component (if applicable):
4.7.1

How reproducible:
Every time when tryion to build the package

Steps to Reproduce:
See the output:
/usr/include/boost/thread/thread_time.hpp:19:24: note: 
âboost::get_system_timeâ
In file included from /usr/include/boost/thread/pthread/mutex.hpp:14:0,
from /usr/include/boost/thread/mutex.hpp:16,
from /usr/include/boost/thread/pthread/thread_data.hpp:12,
from /usr/include/boost/thread/thread.hpp:17,
from /usr/include/boost/thread.hpp:13,
from 
/home/spuhler/Mageia_SVN/kolab-2.4/libkolabxml/BUILD/libkolabxml-0.7.0/src/utils.cpp:33:
/usr/include/boost/thread/xtime.hpp: At global scope:
/usr/include/boost/thread/xtime.hpp:88:1: error: expected declaration 
before â}â token
Comment 1 Manuel Hiebel 2012-07-23 18:36:03 CEST 
fedora has some patch that we don't like like this one http://pkgs.fedoraproject.org/gitweb/?p=boost.git;a=commit;h=f68c4dd92574829a34324290c15e360d0fedf643 maybe that help you ?

(no maintainer of boost btw)
Comment 2 Thomas Spuhler 2012-07-24 16:12:54 CEST 
I believe upgrading to 1.50 will solve it. At least it did at MDV.
Comment 3 Thomas Spuhler 2012-08-05 00:35:55 CEST 
Resolved

Status: NEW => RESOLVED
Resolution: (none) => FIXED
Note You need to log in before you can comment on or make changes to this bug.