Fix build for Void Linux

[faulesocke]

See #58 for details

[faulesocke]

Okay, I think I now have found a better solution. In theory, we could check for all these libraries, but hopefully that's not necessary. @antiagainst I believe this is a working and clean solution now.

[googlebot]

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

📝 Please visit https://cla.developers.google.com/ to sign.

Once you've signed (or fixed any issues), please reply here (e.g. I signed it!) and we'll verify it.

---

What to do if you already signed the CLA

Individual signers

• It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

• Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
• The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
• The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ️ Googlers: Go here for more info.

[antiagainst]

Hey @faulesocke, in order for me to merge this, you'll need to assign the CLA. Also could you rebase against the master? Thanks!

[faulesocke]

Sorry, I don't have a google account so I can't sign the CLA. Also the CLA looks quite complex which is disproportional to the simplicity of my PR.

[mitchmindtree]

I can confirm this patch fixes build issues on Arch Linux as well.

Is there possibly another way to move forward on this? @antiagainst would it possible that you (or someone else who has already signed the CLA) might be able to conveniently come up with a similar solution to this locally and merge a fix yourself? I sympathise with @faulesocke that the CLA is a brutal read for such a simple patch.

[antiagainst]

69adfd6 should fix this. :)

[antiagainst]

Thanks again, @faulesocke !