Globals are not inherently evil, but "shared, mutable state" is, basically if any part of the code is able to scribble over any global at any time.

If your globals are constants, or the globals are only visible inside a single compilation unit where it's easy to keep the situation "contained", they are perfectly fine.