Perhaps converting some of those processes in to shell scripts that invoke libraries which only compile with custom-patched versions of GCC would help. Having the entire set of scripts be solely located in a ZIP file on a tumblr page from 3 years ago would be icing on the cake.

When you're working for a company that has priorities other than you fussing around with your open-source this and open-source that, then naturally the OS X way of doing things becomes easier.

When you're on your own and might appreciate a distraction from the day-to-day coding by, you know, source-patching your open-source media player to fix an irritating bug, the Linux ecosystem provides endless opportunities.

There's a lot to be said for both environments. If you want to be an active participant in building the software you use on a daily basis, Linux is certainly more open in that regard. That's not to say that there aren't a lot of first-class open-source packages on OS X that can be contributed to.