# Partly solved: Could not detect Ninja v1.8.2 or newer **URL:** \ **Category:** mediasoup libraries\ **Created:** [October 21, 2021, 8:37am UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464 "2021-10-21T08:37:58Z")\ **Posts on this page:** 8\ **Page:** 3
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [November 5, 2022, 8:41pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/41 "2022-11-05T20:41:40Z")
mediasoup node 3.11.2 released. It fixes the problem by pining ninja 1.10.2.4. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [November 5, 2022, 8:41pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/42 "2022-11-05T20:41:53Z")
---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [November 5, 2022, 8:59pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/43 "2022-11-05T20:59:35Z")
So the bug is not in Meson but in ninja 1.11.1 (at least in Linux): > On my Linux machine, `ninja --version` doesn’t generate a seg. fault, but it returns error code 245. That is enough to break `meson` , which expects that command to return with error code 0. > > > I just upgraded to 1.11.1, and I get a nonzero return code when I run \`ninja --v…ersion\`: > \`\`\` > $ ninja --version > 1.11.1.git.kitware.jobserver-1 > $ echo $? > 245 > \`\`\` > This is on a Linux system. > > With 1.10.2.4, the return code is 0, as expected: > \`\`\` > $ ninja --version > 1.10.2.git.kitware.jobserver-1 > $ echo $? > 0 > \`\`\` > > This breaks \`meson\`, which expects the return code of \`ninja --version\` to be 0. And the failure of \`meson\` breaks the builds any package that depend on \`meson\`. I noticed this because the CI builds of SciPy are currently failing. ---
**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\ **Post date:** [November 5, 2022, 9:10pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/44 "2022-11-05T21:10:46Z")
I’ll trial and confirm now for you bud! ubuntu 22.04 base install with the following applied. sudo apt update -y sudo apt upgrade -y curl -sL [https://deb.nodesource.com/setup\_16.x](https://deb.nodesource.com/setup_16.x) | sudo -E bash - sudo apt install nodejs -y sudo apt-get install build-essential -y sudo apt install python3-pip -y sudo apt update -y sudo npm install pm2@latest -g sudo npm install -g npm@latest sudo npm install mediasoup – save * * * I had installed mediasoup for a bunch of servers yesterday and no issues, but could confirm this morning as install broke on my development machine. I’ll know in a few minutes if it passes. ---
**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\ **Post date:** [November 5, 2022, 9:27pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/45 "2022-11-05T21:27:27Z")
The install succeeded latest version of media-soup (3.11.2). Would this at all affect previous builds now without some “hacks”? At least this didn’t happen yesterday in my case, ouuf; I was performing reformats on all machines, that would had been so messy hahahahaha. Love the work, if a server is ever needed for mediasoup demo, I got lots of free-space to account for expansion. ---
**Author:** ![ibc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/ibc/32/1540_2.png) [@ibc](https://mediasoup.discourse.group/u/ibc)\ **Post date:** [November 5, 2022, 9:33pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/46 "2022-11-05T21:33:54Z")
> [@BronzedBroth](#): > > The install succeeded latest version of media-soup (3.11.2). Would this at all affect previous builds now without some “hacks”? I’m afraid yes. ---
**Author:** ![BronzedBroth](https://avatars.discourse-cdn.com/v4/letter/b/ad7895/32.png) [@BronzedBroth](https://mediasoup.discourse.group/u/BronzedBroth)\ **Post date:** [November 5, 2022, 9:38pm UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/47 "2022-11-05T21:38:56Z")
Yikes… I hope it’s not to much anxiety for you if there’s pending problems and users use old versions. I so far have no issues but I use simple VP8; I keep to the classics for optimal support. Love the support, IBC you and the team are doing great, I love it. * * * My offer won’t expire as well, you are welcome to use my servers I pool them and can offer up many end-points. Anything to help support. ---
**Author:** ![nazar-pc](https://yyz2.discourse-cdn.com/free1/user_avatar/mediasoup.discourse.group/nazar-pc/32/369_2.png) [@nazar-pc](https://mediasoup.discourse.group/u/nazar-pc)\ **Post date:** [November 6, 2022, 4:30am UTC](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464/48 "2022-11-06T04:30:31Z")
Just FYI for those following this thread, 1.11.1 release of Ninja was also fixed, so regardless of whether you’ve upgraded or not, you should be good now. [Previous page](https://mediasoup.discourse.group/t/partly-solved-could-not-detect-ninja-v1-8-2-or-newer/3464.md?page=2)