Build warning: make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.

[pottendo]

hi,

I recently setup a VM running Ubuntu-24.04.
Building circle-stdlib frequently throws the warning
make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make rule.
when using
$ make -j12

-> falling back to a single-threaded build -> a bit of wasted time in today's setups, where we all have multi-core machines.

I checked a circle standalone build, which doesn't show this effect in Ubuntu/VM.
Further I have another setup (ArchLinux, native x64) which doesn't show this either and fully uses all available cores.

Any idea if the problem is in my setup (Ubuntu/VM) or somewhere in the make-setup of circle-stdlib/circle?
I had a report from a user of one of my projects, who had the same observation (my project is here).

It's not really a priority, but I'm curious and would like to understand and ideally fix it.

Thanks to all circle-stdlib/circle developers - this is great stuff for me to learn and get the max out of my collection of PIs!

thx, pottendo

[smuehlst]

I never bothered because the build time of Circle is short compared to the overall build time, and I thought that it was cumbersome to fix. But you are right, this is annoying, and it was actually easy to fix by simply following the advice in the warning.

Fixed on the master branch. Please give it a try.

[pottendo]

thanks, will try tomorrow...
...forgot to mention: my ArchLinux setup (non VM) throws this warning:
fgrep: warning: fgrep is obsolescent; using grep -F

not sure if from circle, or circle-stdlib...
bye, pottendo

[smuehlst]

...forgot to mention: my ArchLinux setup (non VM) throws this warning:
fgrep: warning: fgrep is obsolescent; using grep -F

A quick fgrep 😄 reveals that this comes from the newlib configure scripts. That is not something I will address myself.

[rsta2]

This message from fgrep comes from Circle (too) and has already been suppressed on the develop branch.

[pottendo]

Thanks, I can confirm that the parallel builds work.
Couldn't check fgrep here, as this warning isn't showing up within the UbuntuVm. I trust this works also! ;-)
bye, pottendo

[smuehlst]

As there are plenty of fgrep calls in the newlib build system, I assume that warnings will still appear during the build of the libs/circle-newlib subdirectory. There are no plans to fix this for the time being.