bfgeshka / octopus Goto Github PK

17:30:59]<MoonchildPM> L29Ah: are you using the recommended toolchain to build Pale Moon?
17:32:19]<L29Ah> gcc (Gentoo Hardened 5.4.0-r3 p1.4, pie-0.6.5) 5.4.0
17:32:49]<L29Ah> it didn't change its behaviour when i moved from 4.9.3
17:32:50]<MoonchildPM> That's a no, then
17:34:18]<MoonchildPM> Please try using gcc 4.9.7; also if you want to build with pie, you must use the --enable-pie config option, not exporting the flags directly.
17:36:39]<L29Ah> i don't export any flags, actually i don't understand how pie is enabled in gentoo since .spec files are gone and $C*FLAGS don't have anything about it
17:37:28]<NewTobinParadigm> mozconfig.. configure options
17:38:40]<L29Ah> i mean, afaik all the executables generated by this compiler are pie by default
17:39:23]<NewTobinParadigm> pastebin or screenshot about:buildconfig for your last build
...
17:39:47]<MoonchildPM> NewTobinParadigm: what he's saying is that the gcc version is use is baking in pie into everything
17:40:11]<NewTobinParadigm> that ... shouldn't be happening
17:41:34]<L29Ah> The Gentoo hardened GCC automatically builds PIEs when building application code, unless explicitly requested not to (with a few built-in exceptions for cases where it is undesirable). The chapter " #PIE describes the toolchain modifications to make this happen, and issues that may arise. 
17:42:12]<NewTobinParadigm> our build system isn't aware of pie by default
17:42:35]<NewTobinParadigm> and I have no idea what the effect pie has on the linked code
17:42:46]<NewTobinParadigm> especially for gcc5+

>>> Installing (2 of 2) app-misc/rmlint-9999::octopus
 * checking 45 files for package collisions
 * This package will overwrite one or more files that may belong to other
 * packages (see list below). You can use a command such as `portageq
 * owners / <filename>` to identify the installed package that owns a
 * file. If portageq reports that only one package owns a file then do
 * NOT file a bug report. A bug report is only useful if it identifies at
 * least two or more packages that are known to install the same file(s).
 * If a collision occurs and you can not explain where the file came from
 * then you should simply ignore the collision since there is not enough
 * information to determine if a real problem exists. Please do NOT file
 * a bug report at https://bugs.gentoo.org/ unless you report exactly
 * which two packages install the same file(s). See
 * https://wiki.gentoo.org/wiki/Knowledge_Base:Blockers for tips on how
 * to solve the problem. And once again, please do NOT file a bug report
 * unless you have completely understood the above message.
 * 
 * Detected file collision(s):
 * 
 * 	/usr/share/glib-2.0/schemas/gschemas.compiled
 * 
 * Searching all installed packages for file collisions...
 * 
 * Press Ctrl-C to Stop
 * 
 * dev-libs/glib-2.50.3:2::gentoo
 * 	/usr/share/glib-2.0/schemas/gschemas.compiled
 * 
 * Package 'app-misc/rmlint-9999' NOT merged due to file collisions. If
 * necessary, refer to your elog messages for the whole content of the
 * above message.

>>> Failed to install app-misc/rmlint-9999, Log file:

>>>  '/var/tmp/portage/app-misc/rmlint-9999/temp/build.log'

 * GNU info directory index is up-to-date.