This usually happens when Manjaro doesn't carry a package that Arch does carry (and that the package you're trying to install from the AUR depends on).

This is always a risk when combining Manjaro with the AUR, as Manjaro is a few weeks behind Arch when it comes to packaging. You can try if the beta repositories have the package, but otherwise you'll just have to wait for Manjaro to update its packages. It'll probably resolve itself, eventually.

You can try looking on the Manjaro forums (I don't see a workaround other than switching to testing/unstable) to check if there's a fix, but please don't bother the Arch/AUR people, they can't help you.

The AUR is for Arch and trying to use it on a different distro will have mixed results at best.

You can either wait for Manjaro to catch up and add the glib2-devel package which was created over a month ago, or edit the plgbuild and change it to glib2

Normally you don't even need AUR for that since it's a core package for Arch. Unless Manjaro did something weird, you should be able to install it via pacman.

However I checked Manjaro packages and glib2-devel is the same version with Arch. Maybe try a whole system update before adding new packages?

I'm confused. Have you tried what is suggested in the arch wiki? Controllers are easier to get working on Linux than in Windows in my experience... And I'm on Manjaro. The Xbox 360 controller was considered the default for such a long time that in many cases, other controllers' buttons had to be remapped externally to match the xbox 360's in order to play games. It should be completely plug and play if your adapter and controller both work.

glib2-devel is a core package and pacman should be able to install it directly. Have you updated your package mirrors and upgraded the system since you installed the machine?