search for: jobserver

...nd LLVMSupport gets built twice for the NATIVE side and twice for the target side, is this the intended behavior? Would it be possible for you to share a cross build log with me so I can compare what I might be doing wrong? And hey, the above mentioned patches did fix 3 out of the 4 "warning: jobserver unavailable: using -j1. Add `+' to parent make rule." messages I was getting. Now I only get this warning when the native llvm-config target starts building. Thanks a lot for all the help! BR, Awais ________________________________________ From: Justin Bogner <justin at justinbogner...

...r/lib/xen/boot/pv-grub-x86_32.gz" make: Leaving directory `/mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/work/xen-4.3.0/stubdom' >>> Completed installing xen-pvgrub-4.3.0 >>> into /mnt/gen2/TmpDir/portage/app-emulation/xen-pvgrub-4.3.0/image/ * QA Notice: make jobserver unavailable: * * make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. * make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. * QA Notice: Package triggers severe warnings which indicate that it * may exhibit...

...Support.a(Process.cpp.o): In function `llvm::sys::Process::GetRandomNumber()': Process.cpp:(.text._ZN4llvm3sys7Process15GetRandomNumberEv+0x70): undefined reference to `llvm::sys::TimeValue::now()' collect2: error: ld returned 1 exit status I also see exactly 4 instances of "warning: jobserver unavailable: using -j1. Add `+' to parent make rule." and this was reported at https://llvm.org/bugs/show_bug.cgi?format=multiple&id=23328 quite some time ago. Has there been any movement on this? Can the mentioned warning cause such a trouble? I doubt that because the warning appears...

While building Samba to target "dist", the build fails with the following error: touch .tmplock WAFLOCK=.tmplock PYTHONHASHSEED=1 WAF_MAKE=1 ./buildtools/bin/waf dist invalid lock file in /usr/src/samba-4.20.2 make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. make[1]: Entering directory '/usr/src/samba-4.20.2/ctdb' touch .tmplock WAFLOCK=.tmplock PYTHONHASHSEED=1 WAF_MAKE=1 ../buildtools/bin/waf manpages invalid lock file in /usr/src/samba-4.20.2/ctdb An empty .tar.gz file is create...

Here''s a simple patch to replace "gcc" with "$(CC)" and "make" with "$(MAKE)". This is required, for example, for Gentoo Linux ebuilds, and it also eliminates a "jobserver unavailable" warning (make-related). -Joe

I also have this questions for this. I wonder if R initiates a system environment or options to instruct the packages on the number of cores to use? It doesn't have to be mandatory for now, but at least package maintainers can have shared consensus and start to adopt this humble settings rather than abusing parallel::detectCores() to max out the number of threads by default. > On Aug 7,

...les for package 'compiler' | Testing examples for package 'parallel' | make[3]: Leaving directory '/build/R-3.5.0/tests/Examples' | make[2]: Leaving directory '/build/R-3.5.0/tests' | make[2]: Entering directory '/build/R-3.5.0/tests' | make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. | running strict specific tests | make[3]: Entering directory '/build/R-3.5.0/tests' | running code in 'eval-etc.R' ... OK | comparing 'eval-etc.Rout' to './eval-etc.Rout.save' ...414,416c414,548 |...

...#39; > | Testing examples for package 'parallel' > | make[3]: Leaving directory '/build/R-3.5.0/tests/Examples' > | make[2]: Leaving directory '/build/R-3.5.0/tests' > | make[2]: Entering directory '/build/R-3.5.0/tests' > | make[2]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule. > | running strict specific tests > | make[3]: Entering directory '/build/R-3.5.0/tests' > | running code in 'eval-etc.R' ... OK > | comparing 'eval-etc.Rout' to './eval-etc.Rout.save'...

...setup archives, but not sure). I have the following RPM's installed: b43-openfwwf-5.2-4.el6.noarch b43-fwcutter-012-2.2.el6.x86_64 I wonder if the kernel update breaks it.. Does any one have experience with this driver and CentOS 6.5? Here is make's output: # make make[1]: warning: jobserver unavailable: using -j1. Add `+' to parent make rule. CFG80211 API is prefered for this kernel version Using CFG80211 API /usr/local/src/hybrid-wl/src/wl/sys/wl_cfg80211.c:64: warning: 'enum tx_power_setting' declared inside parameter list /usr/local/src/hybrid-wl/src/wl/sys/wl_cfg80211...

...build stopped: subcommand failed. So there were some linking issues. Some assistance would be much appreciated. Microsoft's linker has it's version 14.27.29109.0 (VS 2019). Clang's version is clang version 10.0.0 (Target: i686-pc-windows-msvc) Ninja's version is 1.10.0.git.kitware.jobserver-1 Ivan -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20200815/f0e32348/attachment-0001.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: CMakeOutput.log Type: appli...

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 Thanks: Tomáš Golembiovský --- v2v/virt-v2v.pod | 38 ++++++++++++++++++++++++++------------ 1 file changed, 26 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..0943bf305 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,32 @@ that

See this bug for background information: https://bugzilla.redhat.com/show_bug.cgi?id=1350465 --- v2v/virt-v2v.pod | 39 +++++++++++++++++++++++++++------------ 1 file changed, 27 insertions(+), 12 deletions(-) diff --git a/v2v/virt-v2v.pod b/v2v/virt-v2v.pod index e68d75cf8..93d1a9ecd 100644 --- a/v2v/virt-v2v.pod +++ b/v2v/virt-v2v.pod @@ -1909,18 +1909,33 @@ that guest through the RHV-M UI,

If the connection is not local, paths of disks will refer to the remote host, which were mistakenly handled as local paths (in the best case failing to open a non-existing disk, and in the worst case opening a different disk!). In case the disks are remote resources like ssh or ceph, nothing guarantees that the hostname can be reached from the local machine, or even that it is actually the same on

Hopefully this time ...