FWIW make itself does not care about whether there is space after -j or not. Both -j14 -j 14 will result in "-j 14" being added to .MAKEFLAGS (something that really annoys me ;-) So not even a makefile that is attempting to parse .MAKEFLAGS is likely to be screwing things up.
In short; I would expect the -j issue to be a red-herring. David Wolfskill <da...@catwhisker.org> wrote: > On Wed, Oct 02, 2024 at 08:19:25PM +0700, dsdq...@hotmail.com wrote: > > ... > > Just got the same error, but both invocations didn't work, and I noticed > > that bootstrapped version of mtree failed to run because of (now) > > missing libmd.so.6. I think it's not really related to whitespace > > between -j and jobs number, rather you had to (re)build the bootstrap tools. > > Huh; interesting. Well, that last worked for me; a few more details re: > hashes: > > Notes Running Sources > "-j14"; OK main-n272562-33ed9bdca307 main-n272579-3ec4fbdd98f2 > "-j14"; failed main-n272579-3ec4fbdd98f2 > main-n272601-b35f0aa4952c > "-j14"; failed main-n272579-3ec4fbdd98f2 > main-n272615-f5a04b16b189 > "-j 14"; OK main-n272579-3ec4fbdd98f2 main-n272615-f5a04b16b189 > > Also: I have been running with "WITH_META_MODE=yes" since May 2016, at > least. > > Peace, > david > -- > David H. Wolfskill da...@catwhisker.org > Appeasement in 1938 did not bring peace in 1939. > What would appeasement bring now? > > See https://www.catwhisker.org/~david/publickey.gpg for my public key.
