Name: Anonymous 2022-07-16 10:06
and at that level, the functions can never see the big picture: you gotta do the mem secure in the kernel space: not app code
ok
well it's just been a bad 4 weeks with them
i mean every where I went: stonewalled by mac guys
helped by linux and windows guys
makes me appreciate the last 2 so much
Some of this actually was because a mac user asked for a new version of a particular app to be back ported to mac: after the upsteam had dropped support
I said "ok ill do it"
I did get it compiling again on newer mac OSs actually: and running: but that mem secure stuff they did to the C libs brought it down
though for that app the old OSX version still works on newer OSXs: the old compile doesn't trip the memsecure stuff
So I was trying to fufill a request there when that app's upstream wouldn't
But I was just mocked for it.
very draining
I'd never do that kind of porting for a 24/7 job
don't know how people stay sane
How did you guys deal with the changes back in the day?
ok
well it's just been a bad 4 weeks with them
i mean every where I went: stonewalled by mac guys
helped by linux and windows guys
makes me appreciate the last 2 so much
Some of this actually was because a mac user asked for a new version of a particular app to be back ported to mac: after the upsteam had dropped support
I said "ok ill do it"
I did get it compiling again on newer mac OSs actually: and running: but that mem secure stuff they did to the C libs brought it down
though for that app the old OSX version still works on newer OSXs: the old compile doesn't trip the memsecure stuff
So I was trying to fufill a request there when that app's upstream wouldn't
But I was just mocked for it.
very draining
I'd never do that kind of porting for a 24/7 job
don't know how people stay sane
How did you guys deal with the changes back in the day?
