It fucking does. Y'all don't give @davejmurphy enough credit, as far as I can tell devkitppc is the last maintained open source ppc toolchain left and it was for console hacking memes.https://twitter.com/hedgeberg/status/1012226738267545600 …
-
-
Replying to @hedgeberg @davejmurphy
I dunno, I just run `crossdev -t powerpc-elf` and such. Building a GCC cross compiler for any random arch isn't rocket science, there are endless scripts that will do it for you in various shapes and sizes.
2 replies 0 retweets 1 like -
devkitPro is nice for what it's built for, but it has a history of braindead patches and other stuff (e.g. some recent update totally destroyed HBC on real consoles by changing some core type definitions).
2 replies 0 retweets 1 like -
Replying to @marcan42 @hedgeberg
That's not what happened Marcan. Please stop telling lies. I know you don't like me but this crap is beneath you.
1 reply 0 retweets 0 likes -
Replying to @davejmurphy @hedgeberg
Dude, when I released the open source HBC (and made a point of trying to build it with the latest devkitPPC/libogc) I had to spend an hour changing a metric fuckload of of types/printf stuff that had changed. Worked on Dolphin but others said not on real HW.
1 reply 0 retweets 0 likes -
Like, sorry, but there is *no* excuse for changing the size of core types on an established platform. That's a fucking massive ABI-breaking change. You just don't do that.
2 replies 0 retweets 0 likes -
Replying to @marcan42 @hedgeberg
Nobody changed the size of core types Marcan ...
1 reply 0 retweets 0 likes -
As it happens I was talked into patching newlib to remove a warning a long time ago and I shouldn't have done it. Said patch later prevented the toolchain building with updated gcc and it was reverted.
1 reply 0 retweets 0 likes
Yes, that's historically been devkitPro's problem: a whole pile of patches that weren't necessary nor well thought out causing subtle issues. Which is why we used vanilla cross-compilers where libogc wasn't required. Good on you for fixing it, but it still causes pain.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.