https://bugzilla.novell.com/show_bug.cgi?id=692207 https://bugzilla.novell.com/show_bug.cgi?id=692207#c0 Summary: Icecc get stuck during linking without any warning when ICECC_MAX_JOBS=1 Classification: openSUSE Product: openSUSE 12.1 Version: Factory Platform: i386 OS/Version: Linux Status: NEW Severity: Normal Priority: P5 - None Component: Basesystem AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: mailinglists@bluespirit.la QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (Windows NT 5.1; rv:2.0.1) Gecko/20100101 Firefox/4.0.1 The motivation was, that my VMWare was busy with managing the 22 remote compilations (-j22), so that the compile-jobs assigned to itself were the critical path. So I disabled the compilation on my host. After some while I realized, that the linking does not work any more for native compilations. When cross-compiling, I don't use the ICECC for linking. This costs me a lot of time and nerves. So could you add at least an warning: "building locally - but ICECC_MAX_JOBS=0 !!" Thanks a lot, Charly Reproducible: Always Steps to Reproduce: 1. Set ICECC_MAX_JOBS=0 in /etc/icecc/icecc.conf 2. Start compilation (make -j4) -> got stuck on linking Actual Results: g++/icecc got stuck Expected Results: At least an warning - better would be, if the linking is not affected by ICECC_MAX_JOBS - since it cannot be done remotely. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.