On Sun, Jul 15, 2012 at 11:02 PM, Michael Mol <mike...@gmail.com> wrote: > On Sun, Jul 15, 2012 at 9:44 PM, Ezequiel Garcia <elezegar...@gmail.com> > wrote: >> On Sun, Jul 15, 2012 at 4:23 PM, Ezequiel Garcia <elezegar...@gmail.com> >> wrote: >>> On Sun, Jul 15, 2012 at 4:03 PM, Michael Mol <mike...@gmail.com> wrote: >>>> On Sun, Jul 15, 2012 at 2:49 PM, Ezequiel Garcia <elezegar...@gmail.com> >>>> wrote: >>>>> On Sun, Jul 15, 2012 at 3:45 PM, Michael Mol <mike...@gmail.com> wrote: >>>>>> On Sun, Jul 15, 2012 at 2:33 PM, Ezequiel Garcia <elezegar...@gmail.com> >>>>>> wrote: >>>>>>> Michael, >>>>>>> >>>>>>> On Sun, Jul 15, 2012 at 3:25 PM, Michael Mol <mike...@gmail.com> wrote: >>>>>>>> On Sun, Jul 15, 2012 at 1:50 PM, Ezequiel Garcia >>>>>>>> <elezegar...@gmail.com> wrote: >>>>>>>>> While trying to emerge gnash, I was forced to emerge --update boost. >>>>>>>>> >>>>>>>>> But it failed! (I was actually doing emerge --deep --update @world) >>>>>>>>> >>>>>>>>> I set MAKEOPTS="" as suggested to prevent multiple build jobs. >>>>>>>>> >>>>>>>>> >>>>>>>>> So, here are last words. They don't say anything to me :-( >>>>>>>>> -------------------------------------------------------------------- >>>>>>>> >>>>>>>> [snip] >>>>>>>> >>>>>>>> In the future, please attach, rather than in-line, stuff like build >>>>>>>> logs. >>>>>>>> >>>>>>> >>>>>>> Okey. Thanks for the tip and sorry for the trouble. >>>>>>> >>>>>>>> Here's what's killing it for you: >>>>>>>> >>>>>>>>> In file included from ./boost/thread/detail/platform.hpp:17:0, >>>>>>>>> from ./boost/thread/mutex.hpp:12, >>>>>>>>> from libs/locale/src/shared/date_time.cpp:11: >>>>>>>>> ./boost/config/requires_threads.hpp:29:4: error: #error "Threading >>>>>>>>> support unavaliable: it has been explicitly disabled with >>>>>>>>> BOOST_DISABLE_THREADS" >>>>>>>>> In file included from ./boost/thread/mutex.hpp:12:0, >>>>>>>>> from libs/locale/src/shared/date_time.cpp:11: >>>>>>>>> ./boost/thread/detail/platform.hpp:67:9: error: #error "Sorry, no >>>>>>>>> boost threads are available for this platform." >>>>>>>> >>>>>>> >>>>>>> Oh! I missed it. Thanks a lot for going through this. >>>>>>> >>>>>>>> I'm not going to venture a guess as to why this is happening on your >>>>>>>> system. But there's the explicit build error, cut out from the rest of >>>>>>>> the log. >>>>>>>> >>>>>>> >>>>>>> I think I've hit this bug: >>>>>>> >>>>>>> https://svn.boost.org/trac/boost/ticket/6165 >>>>>>> >>>>>>> It's gcc 4.7 related. I'll try to apply the patch suggested here: >>>>>>> >>>>>>> https://svn.boost.org/trac/boost/changeset/76133 >>>>>>> >>>>>>> and let you know. >>>>>>> >>>>>>> As I've never patched an ebuild, this might take me some time :-( >>>>>> >>>>>> Hey, whaddaya know, my first was last week. I got some great help in >>>>>> the #gentoo-chat IRC channel. I'll send you a transcript off-list, and >>>>>> a link to my b.g.o entry. >>>>>> >>>>> >>>>> Great! I already have the patch, but putting it into >>>>> /etc/portage/patches didn't work :-( >>>> >>>> Read the transcript; it goes through how you create a private overlay >>>> and verify that portage is using it. >>>> >>> >>> ok, tons of thanks. >> >> Worked like a charm, following your instructions. >> >> I'll open now a bug and attach the upstream patch. > > Thank Mike Gilbert (floppym) for the instructions. I simply have > logging enabled in my IRC client and knew how to use grep. :) > > Glad to hear it helped, though! >
I was just about to open a bug until I found this one: https://bugs.gentoo.org/show_bug.cgi?id=407761 It sounds sensible to *not* fix this in boost-1.48, since gcc-4.7 was hard masked anyway. So, I've unmasked boost-1.49, instead of using patched 1.48. But, I've learned how to patch and prepare a private overlay; so this made my day :-) Thanks and see ya, Ezequiel.
