Re: [gentoo-user] GCC 10.1 SUCKS.

[Sergei Trofimovich <slyfox@gentoo.org>]

On Thu, 14 May 2020 11:15:59 -0400
Alan Grimes <alonzotg@verizon.net> wrote:

> KDE really can't update itself, I really had to flog the living bleep
> out of it to get it, and a lot of other stuff to settle down...
> 
> The configure phases for most of these packages are so monsterously
> inefficient that I have to run dozens of builds concurently to get CPU
> utilization out of the single digits... Okay, I have a high-end
> processor rn but it's crazy watching the actual compile stages of
> various packages only blip the histogram for a fraction of a second...
> 
> Here are some highlights from the fails that I consider "hard fails":
> 
> Dependency of libreoffice: Libetonyek 
> 
> 
>  -I/usr/include/libxml2  -DNDEBUG -DLIBETONYEK_VISIBILITY
> -fvisibility=hidden -march=native -pipe -O3  -Wall -Wextra -Wshadow
> -pedantic -Weffc++ -c -o
> contexts/libetonyek_internal_la-IWORKLayoutElement.lo `test -f
> 'contexts/IWORKLayoutElement.cpp' || echo './'`context
> s/IWORKLayoutElement.cpp
> /bin/sh ../../libtool  --tag=CXX   --mode=compile
> x86_64-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I../.. 
> -DBOOST_SPIRIT_USE_PHOENIX_V3  -DLIBETONYEK_BUILD -I../../inc
> -I../../src/lib/contexts   -I/usr/include/libxml2
> -I/usr/include/mdds-1.5 -I/usr/include/librevenge-0.0
>  -I/usr/include/libxml2  -DNDEBUG -DLIBETONYEK_VISIBILITY
> -fvisibility=hidden -march=native -pipe -O3  -Wall -Wextra -Wshadow
> -pedantic -Weffc++ -c -o
> contexts/libetonyek_internal_la-IWORKLineElement.lo `test -f
> 'contexts/IWORKLineElement.cpp' || echo './'`contexts/IW
> ORKLineElement.cpp
> NUM3Parser.cpp: In member function ‘virtual bool
> libetonyek::NUM3Parser::parseDocument()’:
> NUM3Parser.cpp:46:8: error: ‘for_each’ is not a member of ‘std’
>    46 |   std::for_each(sheetListRefs.begin(), sheetListRefs.end(),
> std::bind(&NUM3Parser::parseSheet, this, std::placeholders::_1));
>       |        ^~~~~~~~

Please file bugs to bugs.gentoo.org and maintainer should help you.

In this case it looks like a https://bugs.gentoo.org/722042 which
was a boost update.

-- 

  Sergei