It's quite a bad UX, but generally error 2 from make means the called program resulted into an error.
Usually this is accompanied with another error somewhere up the log. Multiple cores can make this a challenge to scan the log for however, so maybe try compiling without the -j argument, that should get the actual error closer to the end.
From my experience, it's usually an outdated config for the kernel (like using a config for 5.1 while compiling 6.7) or a missing dependency. However the real error will be somewhere among the logs, who knows, maybe it's a missing processor instruction (it's really bad UX).
In C exit codes are numbers, in the Makefile it says line n° 2014, error 2 probably has some kind of special meaning, you could take a look and search from there.
Look at the build output for the error. Run the build again with "-j1" if neccessary.
Also, try searching the web before crying on social media. If you can't solve your problems without being spoon-fed then GNU/Linux probably isn't for you.