1) Second mac mini 2011 version arrived. 2) Tested it out. works.
3) No OSX mountain lion install iso's work Entire night used up trying ones, until find one that works from india. (Nahrim version).
4) Doesn't shut down cleanly, ever, even with shutdown -h now. So always have complaining "u didn shutdown rite" every startup. Mountain Lion is the version this 2011-2012 mac uses naitevly. Always have to manually kill the power as it NEVER shuts off all the way. Have to hold down power button for a year to have it turn on.
5) Downloads the OSX 8.5.x update. Fails to install.
6) Installs xcode-command-line tools. Only 1 of 2 victories.
7) WILL NOT INSTALL 4.5 xcode for mountain lion. Errors out 85 percent in.
6) Mac ports installs. Won't install gcc or glfw because no xcode (even though the command line stuff IS installed).
7) "homebrew" just says "Your OSX is too old" and quits. Fucking faggot. Reminds me of some people I know.
So nothing FUCKING works. I CANNOT get my game compiled and running correctly NO MATTER WHAT.
I got the right versions and get FUCKED anyway. I hate you fucking people.
And where the fuck is the mac guy that said "please make a mac binary for us"? Where the fuck is he? Laughing at me?
This is to get around the adulterations apple made to the standard c libraries which break the engine when it runs (strlcpy). Which NONE of you help with either.
And no: I am not going to make a "minimum reproducable build". I know what the problem is. You would too if you read the rundown. Fucking faggots. I'm not your "coding cubicle open plan office worker collegue bud". Fix the fucking issue with a macro and post it here or don't. I know you know what the macros would be for this. Since I know I'm not the only one who had this problem.
I see some retarded cartoon for kids. I'm not even apple faggot
Wyatt Powell
HEY MAC FUCKING DIP SHITS.
ARE YOU GOING TO TELL ME WHY THE XCODE INSTALLER I DOWNLOADED THAT SAYS IT IS FOR OSX MOUNTAIN LION
_DOES NOT FUCKING WORK_ AND ERRORS OUT.
_AND WHY I CANNOT FUCKING USE EVEN GCC WITHOUT XCODE-FULL ON OSX MOUNTAIN LION_
_ARE YOU?_
Or is this what you wanted when you said "hey make a new OSX build"
Levi Moore
It really is. Classic Mac OS was nice though. OSX was never as fun to use and became worse with each version.
Christopher Carter
>I see some retarded cartoon for kids. >I'm not even apple faggot
It's a Any Forums banner. This is an anime website. Get the fuck out if you don't like anime. Or we'll have the Russians kill your kind. Your choice dipshit.
>kys you disgusting pedo YHWH explicitly allows child brides. (5th book of Moses, chapter 22, verse 28, in Hebrew, Greek, and Latin (not english)) You are disgusted by what is beautiful. Cute little girls are beautiful.
I'm just telling you to check if it's a compile time option in your makefile that's making your strcpy behave weirdly or it's the default behavior of OSX's libc. What solution using macros are you thinking about? Just checking if you're compiling for macos before every strcpy and instead using your own implementation? That'd be a very ugly fix but I guess you could do it using find and replace. Or maybe there's some a simpler way to replace libc functions with your own implementation. Maybe by giving some special options to the linker to prioritize your own function. Or does it just link to the first .so implementing any given function? If it works like that then it'd be fairly easy to add your own .so containing your implementation of strcpy. I don't have a mac but it's an interesting issue.
Hudson Moore
Tech support threads are against the rules.
Nolan Murphy
>It really is. Classic Mac OS was nice though. OSX was never as fun to use and became worse with each version.
Classic mac didn't have retarded "memory protections" baked into the standard BSD C libs either (wrong place for that: the correct place is in the kernel: anyone wanting to circumvent these "protections" can simply use another c lib statically compiled in for their "hax0rs" binary. Grsecurity-linux and NetBSD's KALSR and OpenBSD do it right. As does Windows mem protection now. But not apple)
>I'm just telling you to check if it's a compile time option in your makefile that's making your strcpy behave weirdly or it's the default behavior of OSX's libc.
It's the default behavior of OSX's lib C. They made it so you couldn't copy a string to a memory address that had the "same" string. Why, who knows. Doesn't increase security at all; and adulterates 20/30 years of OpenBSD's code.
They did it in Mavericks I was told. The old compile of this game doesn't have the problem (even when running on new macs), so it's a change they made.
Also it runs fine without changes under grsecurity-linux.
>Tech support threads are against the rules. Go to hell.
>Cute little girls are beautiful. Yes, and that's why would-be rapists like you should rot in prison or closed psych ward so that you won't hurt them.
Brayden Stewart
>wrong place for that: the correct place is in the kernel: anyone wanting to circumvent these "protections" can simply use another c lib statically compiled in for their "hax0rs" binary. The point of memory protections in the standard library is that buggy programs can't be exploited as easily by giving it specially crafted input data. In that situation the attacker wouldn't be able to just change the binary by a malicious one. In this case I'm not sure what the issue is, did you say that strcpy errors out when the input pointer is the same as the output pointer? Or when the copied memory regions overlap? I suppose the logic is that if your output pointer is input+n, you would overwrite your null terminator. But is it really doing that? Because that way of doing strcpy would be pretty inefficient, since you would have to first find the null terminator to get the length of the input string, and only then can you check if you are overwriting part of it.
Julian Williams
>Or rather, Russians will kill animefags. Russians might kill everyone: but they like anime themselves.
>Yes, and that's why would-be rapists like you should rot in prison or closed psych ward so that you won't hurt them. A toy should be used. Not rot on a shelf.
Girls were made by YHWH as toys for men to own. Faggots such as you disagree. That's the fundamental malfunction of faggot hooiser christianity that is america. And whatever offshoots it has had over the previous 150 years since the christian temperance cunt movement starting with the married woman's property act.
We'll help the Russians kill you fucking scum: even if we die too. Which we will.
>They made it so you couldn't copy a string to a memory address that had the "same" string. What does that actually mean. That you can't copy a string to a memory location that's within the input string? Because that would be what I just descried. You would overwrite your null terminator. Or do you mean that you can't copy to a location before the start of the input string, but in a way that the output overlaps with the beginning of the input? Because that would be safe and there's no reason to prevent it. If both input and output are the same then it should be safe as well.
Kayden Jenkins
>A toy should be used. Not rot on a shelf. >Girls were made by YHWH as toys for men to own. As I've said: you're a disgusting pedophile and should be locked up before you hurt someone.
Gabriel Mitchell
How do you make the textures for the models in your game? GIMP? Do you paint them manually or what? Do you use a drawing tablet or a mouse? Or do you download pre-made textures from somewhere?
Jayden Wright
>The point of memory protections in the standard library is that buggy programs can't be exploited as easily by giving it specially crafted input data. In that situation the attacker wouldn't be able to just change the binary by a malicious one.
Everyone else does it in the kernel. Grsecurity pioneered this. It's the correct way. Apples rape of the OpenBSD standard libraries is unconscionable. And it will be revenged when the Russians get here.
I am not going to listen to you criticized John Carmack's and Lord Havoc's code because it's not "forward thinking" enough for apple faggots who are adulterating the standard libraries instead of putting real memory protections in the kernel.
I'm not going to answer why this or that is done. It's simply that there are standard default values in the code if a texture or other thing is missing. But when you use that default texture intentionally the two match up. There was never a need nor a reason to hyperventilate checking if the values were the same. Untill fucking literal dick-chopped-off apple faggots committed adultery.
That is they adulterated OpenBSD's long standardized-by-practice strlcpy function. They mixed in their faggotry and lack of kernel hacking talent.
>How do you make the textures for the models in your game? GIMP? Do you paint them manually or what? Do you use a drawing tablet or a mouse? Or do you download pre-made textures from somewhere?
I go somewhere in my house that has the marble that I want and I take a picture. Then I use the gimp.
I used to draw them in the gimp 20 years ago. But now usually pictures taken with my Nikon DSLR with 1970s glass that cost 2 dollars.
