Slic3r compilation update. It turns out that a new version of the OpenGL lib came out less than a week ago. It breaks the gui. The version you should use is 0.6704 but the slicer build script automatically updates it, because why not.
So to fix, you need to edit the Build.pl and delete the line that searches for OpenGL. If it’s already installed 0.70 then goto the perl opengl 2 sourceforge site and use cpanm mytar.gz to install the older version.
The other errors I had was from boost. If all else fails delete boost and recompile.
Of course, none of this fixed amf parsing. I no longer get an error that it’s unsupported, instead it has a parsing error.
Yeah. I wanted to work on Slic3r a number of years ago and there was just too much pain for my desire. Good luck and I hope you do neat things.
Lol I’m not much of a contributor, just trying to get it to compile with amf support. Anyways, it works in a way. I didn’t know amf was an xml based format, but apparently there is a binary version too that slic3r doesn’t support.
Soo, just wondering where I can find information on that format now.
But switching to slic3r is worth it. It’s more accurate and more configurable.
Think I found it, amf supports a zipped format as binary. So all that needs to be added is an unzip method to detect if the file is plain text or zip, then unzip and parse.
Luck is becoming part of the deal nowadays…
Actually I switched to Slic3r two nights ago… precisely because I had no time to spend again fighting with the broken/touchy dependencies of the Cura linux package! 
In my case, Slic3r was a breeze to build (I am on linux Xenial).
What bugged me for the last coupel of months is a slow/buggy OpenGL when using Openscad (but I do not think it is linked to Openscad itself on my box).