Summary: | app-office/openoffice-3.1.1 compile error using sys-devel/gcc-4.4.2 in dev-libs/boost-1.35.0-r2 include /usr/include/boost/mpl/apply_wrap.hpp | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michael Weber (RETIRED) <xmw> |
Component: | Current packages | Assignee: | Gentoo Office Team <office> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | alon.barlev, mescalinum, SebastianLuther |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | AMD64 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
build.log part 1 of 2
build.log part 2 of 2 |
Description
Michael Weber (RETIRED)
2009-10-24 09:59:11 UTC
Created attachment 208129 [details]
build.log part 1 of 2
Created attachment 208130 [details]
build.log part 2 of 2
ok, this seems to be an incompartibility of <boost-1.37 with gcc:4.4. I've switched to gcc:4.3 to reemerge boost-1.35.0 and then to gcc:4.4 to reemerge openoffice. The failing point in ... is changed from ///// iteration, depth == 1 #elif BOOST_PP_ITERATION_DEPTH() == 1 # define i_ BOOST_PP_FRAME_ITERATION(1) to ///// iteration, depth == 1 // For gcc 4.4 compatability, we must include the // BOOST_PP_ITERATION_DEPTH test inside an #else clause. #else // BOOST_PP_IS_ITERATING #if BOOST_PP_ITERATION_DEPTH() == 1 # define i_ BOOST_PP_FRAME_ITERATION(1) . I'm running two slots of gcc due to many gcc:4.4 incompartibilities. I can't figure out how to represent this bug inside the ebuilds, one would have to detect the compiling gcc dynamically during build and request the correct boost version. Or, maybe just stabilie boost:1.39, Related http://bugs.gentoo.org/show_bug.cgi?id=289799 I get something else... boost/shared_ptr.hpp cannot be found. Workaround: CPPFLAGS="-I/usr/include/boost-1_35" emerge --oneshot openoffice (In reply to comment #4) > I get something else... > > boost/shared_ptr.hpp cannot be found. > > Workaround: > CPPFLAGS="-I/usr/include/boost-1_35" emerge --oneshot openoffice > Solution: eselect boost set 1 *** Bug 290504 has been marked as a duplicate of this bug. *** Is here something left to fix? (In reply to comment #7) > Is here something left to fix? upgrading boost + eselect boost set 1 worked for me ooops, I was speaking for bug 290504 Closing this. This is fixed in >=boost-1.35.0-r5. |