New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PowerPC] CoreAudio
output does not work; specific optflags needed to produce a working app
#658
Comments
After disabling CoreAudioOutput plugin (CoreAudio should be supported on 10.5/10.6, but this is just for debugging), I got TUI starting up, but then it still crashes:
@clangen If you could take a look, it would be very helpful. |
Running the same via GDB, I get this:
Backtrace is incomplete for some reason:
|
Crash log:
|
@clangen So depending on slight changes with build settings, I either get no TUI and a crash on CoreAudio, or TUI startup and crash on some conversion procedure.
If there an easy way to switch it to using Boost locally, to compare the behavior? P. S. Usual suspects for this kind of failures are endianness, bitness and 4-byte bools and spinlocks. Any of these could be relevant here, what do you think? |
@clangen Okay, I have actually fixed it. This is one problem I noticed immediately – CoreAudio output is broken, i.e. everything builds fine, but instead of music I get just hissing noise. However, PortAudio output works perfectly fine. (I did not try any fancy audio formats, just picked a regular mp3 for quick testing.) Basic functionality seems working. |
Macports now has the updated version which should work on PowerPC systems: https://github.com/macports/macports-ports/blob/e29e07d0b9373354cd9bdd748a8a208fbecb8fd3/multimedia/musikcube/Portfile Two issues remain:
|
musikcube
fails to run on PowerPC: KERN_INVALID_ADDRESS at address: 0xfffffff4
CoreAudio
output does not work; specific optflags needed to produce a working app
After fixing
libatomic
linking and ObjC (needs extra flags to work), everything built fine, but the binary fails:Something broken about endianness?
The text was updated successfully, but these errors were encountered: