>Errors: pastebin.com
I'm bought a 69 dollar refurbished 2011 i5 mac mini (8gb ram). I don't know anything about OSX: I usually use linux, and sometimes windows. My work compiled fine on Linux, both 32 bit and 64 bit, and Windows, 32 bit and 64.
Linux took 0 days: was easy. Windows took 1 day per architecture. So 2 days really.
OSX : it's been a week since I got the thing; i STILL CANNOT PRODUCE A FKING BINARY.
The C files seem to compile now but WILL NOT LINK.
I do NOT understand why because OSX is "not my jam" as a mac user might say (I do like longboards with 110 mm wheels though: so something in common dear mac people that maybe reading).
I was asked by a mac user to make binaries of my game for mac. SO that is why I bought the mac mini. The last binary of this software .app on OSX that I have was from 2012: so I got a 2011 mac mini and it has High Sierra on it. I wanted to use the same thing that was last used on. The CODE is ALMOST THE SAME AS THEN: because my project forked in 2012 and we just add code we write like to load Wolfenstine: Enemy Territory maps.
So it's the same code that WORKED IN 2012 and the SAME MAKE FILES. I do NOT KNOW WHY I CANNOT FUCKING LINK THEM. WHY DOES IT FUCKING FAIL.
I don't know OSX.
I installed mac ports as the nice mac person said and that got it compiling the actual code and not erroring out looking for SDL2 3d gl thing or whatever.
But it WILL __NOT__ LINK.
I don't know what to do: because I do not know clang, I don not know OSX, I just don't fucking know this shit.
I know Linux. GCC, C, Perl, PHP, Python, and Quake C. I do NOT KNOW CLANG. I DO NOT KNOW OSX. Windows was easy enough to compile on using MSYS (for 32 bit) and MSYS2 (for 64 bit)
WHAT DO I DO.
I want to know before I turn the mac on again and fucking go absolutly fucking InSAnE when it FUCKING FAILS NO MATTER WHAT I FUCKING FUUUUCCCCKKKKK DO!!!
So please let me know How i fucking compile this fucking fuck fuck fucckkkk.
