McQ Posted August 12, 2017 Report Share Posted August 12, 2017 Had a failure today when upgrading to subversion-1.9.7: hmod 755 blib/arch/auto/SVN/_Wc/_Wc.so "/usr/bin/perl" -MExtUtils::Command::MM -e 'cp_nonempty' -- _Wc.bs blib/arch/auto/SVN/_Wc/_Wc.bs 644 Manifying 8 pod documents make[2]: Leaving directory '/var/tmp/portage/dev-vcs/subversion-1.9.7/work/subversion-1.9.7/subversion/bindings/swig/perl/native' make[1]: Leaving directory '/var/tmp/portage/dev-vcs/subversion-1.9.7/work/subversion-1.9.7/subversion/bindings/swig/perl/native' Makefile:850: recipe for target 'swig-pl' failed make: *** [swig-pl] Error 2 * ERROR: dev-vcs/subversion-1.9.7::dev-kit failed (compile phase): * emake fail So I changed in /etc/portage/make.conf: (-)MAKEOPTS="-j5" (+)MAKEOPTS="-j1" And then subversion package compiled without any issue. Should I just leave make.conf as is or switch back to MAKEOPTS="-j5" ? I really don't know if the difference is worth maintaining for system-wide. Link to comment Share on other sites More sharing options...
0 Sandro Posted August 12, 2017 Report Share Posted August 12, 2017 The "Default" is "-j2" (the rule is n? threads + 1) I think is better to have MAKEOPTS="-j5" in /etc/make.conf and if you got errors, to try for example # MAKEOPTS="-j1" bla_bla_bla.version But in your case i will make a serious ramt3est. Cause it is impossible to have all these errors. Or if You have overclocked the system to return to "default". If your system isn't overclocked .... i think that You can have some trouble with rams. Funtoo have the memtestX86; but you can use other DVD/CD ... for example the "SysrescueCD". Link to comment Share on other sites More sharing options...
0 McQ Posted August 12, 2017 Author Report Share Posted August 12, 2017 Thanks for the tip! System is not overclocked and the memtest found no errors. It must just be a package-specific issue. I'll go back to MAKEOPTS="-j5" in make.conf. Link to comment Share on other sites More sharing options...
0 Sandro Posted August 14, 2017 Report Share Posted August 14, 2017 McQ: Another thing is about the temoperatures ..... when you use the Jobserver (Makeops) = -j5, take a look about cpu temperatures, for example in a terminal: $ watch sensors To install it: # emerge lm_sensors # sensors-detect # rc-update add lm_sensors default # openrc (I wish to be not too pedantic :D otherwise i must use "# USE="-pedantic emerge -e sandro" :D :D :D Ciao :) Link to comment Share on other sites More sharing options...
0 McQ Posted August 15, 2017 Author Report Share Posted August 15, 2017 McQ: (I wish to be not too pedantic :D otherwise i must use "# USE="-pedantic emerge -e sandro" :D :D :D Ciao :) Haha! I like it --- thanks. i3 CPU is at 66? C in sunny Phoenix with a 140 mm USB Fan venting the laptop. Link to comment Share on other sites More sharing options...
0 Sandro Posted August 16, 2017 Report Share Posted August 16, 2017 McQ Also i like your friendship :) .... sorry ... i've not other ideas about the reason related to the failure using the "Full Jobserver" :| Sob :( Link to comment Share on other sites More sharing options...
Question
McQ
Had a failure today when upgrading to subversion-1.9.7:
So I changed in /etc/portage/make.conf:
And then subversion package compiled without any issue.
Should I just leave make.conf as is or switch back to MAKEOPTS="-j5" ?
I really don't know if the difference is worth maintaining for system-wide.
Link to comment
Share on other sites
5 answers to this question
Recommended Posts