On Thu, Apr 14, 2016 at 10:24:05AM +0200, Stefan Richter wrote: > On Apr 14 Stefan Richter wrote: > > gcc (Gentoo 4.9.3 p1.2, pie-0.6.3) 4.9.3" > > [...] > > Build log: http://pastebin.com/fRHScVVH > > > > Not sure what changed since the last successful build. gcc was possibly > > the same. > > Build fails in the same way with gcc (Gentoo 4.8.5 p1.3, pie-0.6.2) 4.8.5.
Current svn builds fine for me in Slackware 14.1: gcc 4.8.2, libxml++ 2.37.2, dbus-c++ git from Nov 2014, glibmm 2.36.2. My compilation lines do *not* include "-std=c++11", so I wonder whether the presence of that is the root cause for the trouble. My typical g++ call is g++ -o src/dice/dice_avdevice.os -c -m64 -Wall -g -Werror -fPIC -fPIC ... This is in a multilib x86_64 environment, so "-m64" is expected. I don't think the "-std=c++11" should be specified; it would be interesting to query the ebuild commit log to see what reason was given when it was added (assuming that this is where it's coming from). Is there a way for you to hack the build script to get rid of it so this theory can be tested? Also, following up on my earlier comment about libxml++, I checked my logs and the problem I was thinking about wasn't a compilation error, but was related to the chasing the cause of warnings in a couple of libraries. It's therefore not relevant here. Regards jonathan _______________________________________________ Linux-audio-dev mailing list Linux-audio-dev@lists.linuxaudio.org http://lists.linuxaudio.org/listinfo/linux-audio-dev
