Created attachment 317878 [details] emerge -av rox-lib with errors on compilation When emerging rox for the rox file manager, I get these really ugly errors that tells me either rox-lib didn't compile, or something is not going to work right later on. Please see the attached file. In the messages below, it specifically says to report a bug on this ebuild. bullshark@beastlinux ~ $ emerge --info | vpaste bg=dark http://vpaste.net/RgBr7 bullshark@beastlinux ~ $ Then, if the debug messages are not clear enough, I can recompile without -fomit-frame-pointers Some additional info on my Gentoo system: http://vpaste.net/2a6im Also, I am using the hardened stage3 tarball (autobuild current)
(In reply to comment #0) > Created attachment 317878 [details] > emerge -av rox-lib with errors on compilation > > When emerging rox for the rox file manager, I get these really ugly errors > that tells me either rox-lib didn't compile, or something is not going to > work right later on. Please see the attached file. Thanks for that attachment. > In the messages below, it specifically says to report a bug on this ebuild. > > bullshark@beastlinux ~ $ emerge --info | vpaste bg=dark > http://vpaste.net/RgBr7 Please attach that too. > Then, if the debug messages are not clear enough, I can recompile without > -fomit-frame-pointers > > Some additional info on my Gentoo system: > http://vpaste.net/2a6im And that. If you can do it once, you can do it three times.
Ok...geeze
Created attachment 317880 [details] Some additional info on my Gentoo system
Created attachment 317882 [details] emerge --info
Is my bug valid now? I have all files as attachments.
For anybody else having this bug, just eselect your python to python2.7, and don't both bug posting on here, devs will get rude and then not want to fix shit.
The warning was dropped from eclass
