Previous Thread
Next Thread
Print Thread
Page 3 of 10 1 2 3 4 5 9 10
Joined: Oct 2004
Posts: 17
L
L66 Offline
Member
Offline
Member
L
Joined: Oct 2004
Posts: 17
It's a mystery indeed. I've asked someone owning a 32 bit MacBook to test, and AO 2.0 launches just fine on that. I can't imagine XCode would just drop 32 bit PPC support and keep 64 bit support for Carbon apps either.

Oh well.

EDIT: Apparently it did just that:

Code:
Mac-mini:~ l66$ lipo -detailed_info /Emulation/Audio\ Overload\ v2.0/Audio\ Overload.app/Contents/MacOS/Audio\ Overload 
Fat header in: /Emulation/Audio Overload v2.0/Audio Overload.app/Contents/MacOS/Audio Overload
fat_magic 0xcafebabe
nfat_arch 2
architecture i386
    cputype CPU_TYPE_I386
    cpusubtype CPU_SUBTYPE_I386_ALL
    offset 4096
    size 3073308
    align 2^12 (4096)
architecture ppc970
    cputype CPU_TYPE_POWERPC
    cpusubtype CPU_SUBTYPE_POWERPC_970
    offset 3080192
    size 3194176
    align 2^12 (4096)


The 2.0b9 version lists
Code:
Mac-mini:~ l66$ lipo -detailed_info /Emulation/Audio\ Overload\ v2.0b9/Audio\ Overload.app/Contents/MacOS/Audio\ Overload 
Fat header in: /Emulation/Audio Overload v2.0b9/Audio Overload.app/Contents/MacOS/Audio Overload
fat_magic 0xcafebabe
nfat_arch 2
architecture ppc
    cputype CPU_TYPE_POWERPC
    cpusubtype CPU_SUBTYPE_POWERPC_ALL
    offset 4096
    size 3054440
    align 2^12 (4096)
architecture i386
    cputype CPU_TYPE_I386
    cpusubtype CPU_SUBTYPE_I386_ALL
    offset 3059712
    size 2855212
    align 2^12 (4096)


I'm sure you already know though. Knowing you didn't and never would specifically target ppc64 it's indeed a complete mistery.

Well, being unable to provide any more info as a generic user with no coding know how at all I'll just let this rest. G5 support works for me, and I probably get rid of that machine anyway before Snow Leopard arrives (which just may drop PPC support entirely according to the rumors). If Apple would have just announced the switch sooner I wouldn't have invested in that machine at all. That was a lot of money that went down the drain seeing how the PPC programs I wanted to use on it either cancelled or dropped support, also thanks to the PCI/PCI-X/PCI-e switch around that time. At least I don't have the PCI-X version. The 8 GB of RAM wasn't too cheap either back in 2005.
No, I think I just get a cheap Intel machine, and keep my G4 MDDs for work. They also run my OS 9 programs (sadly, many good apps never made it to OS X, they either died or went to Windows), making the G5 looking even more useless and pathetic. The Intel machines, on the other hand, can run Windows natively and safely. Might be worth looking into. [/rant]

Last edited by L66; 08/06/08 07:40 PM. Reason: Added a bunch of text
Joined: Dec 1969
Posts: 906
Senior Member
OP Offline
Senior Member
Joined: Dec 1969
Posts: 906
Well that just proves it. Xcode is set to generate ppc and i386, not ppc970 and i386. Sodomy non sapiens.

Joined: Feb 2004
Posts: 312
A
Senior Member
Offline
Senior Member
A
Joined: Feb 2004
Posts: 312
ppc970 != ppc64. You can make a 32 bit ppc binary that only runs on G5s.

Somehow, you've built it targeting G5s. So, for example, gcc will emit instructions not supported on G4 (vector sqrt etc), and schedule instructions for 5 dispatch slots.

Look at the build log in Xcode's build tab-- it'll have -arch ppc970 or -mcpu=ppc970 in there. Find the culprit in the target or project build settings and fix it.

If you're Leopard-only, then ppc7400 is OK. If earlier, use ppc.


Joined: Dec 1969
Posts: 906
Senior Member
OP Offline
Senior Member
Joined: Dec 1969
Posts: 906
I repeat. Xcode is NOT set to build for G5. All the project settings are shown on G4.

CompileC "build/AudioOverload.build/Build/Audio Overload.build/Objects-normal/ppc/mac-file.o" "/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/../mac/mac-file.c" normal ppc c com.apple.compilers.gcc.4_0
cd "/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project"
/Developer/usr/bin/gcc-4.0 -x c -arch ppc -fmessage-length=0 -pipe -std=c99 -Wno-trigraphs -fpascal-strings -fshort-enums -fasm-blocks -O3 -mdynamic-no-pic -Wunknown-pragmas -isysroot /Developer/SDKs/MacOSX10.4u.sdk -mtune=G4 -mpowerpc64 -fvisibility=hidden -mmacosx-version-min=10.4 "-I/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/build/AudioOverload.build/Build/Audio Overload.build/Audio Overload.hmap" "-F/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/build/Build" -F/Developer/SDKs/MacOSX10.4u.sdk/System/Library/Frameworks "-I/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/build/Build/include" -I/Developer/SDKs/MacOSX10.4u.sdk/Developer/Headers/FlatCarbon "-I/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/build/AudioOverload.build/Build/Audio Overload.build/DerivedSources" -c "/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/../mac/mac-file.c" -o "/Users/richardb/Documents/Programming/Emulation/Audio Overload 2/Project/build/AudioOverload.build/Build/Audio Overload.build/Objects-normal/ppc/mac-file.o"


Joined: Feb 2004
Posts: 2,194
Very Senior Member
Offline
Very Senior Member
Joined: Feb 2004
Posts: 2,194
And there's the problem - see the -mpowerpc64 flag in there? It's building for 32-bit ABI but enabling the use of 64-bit instructions.

Joined: Dec 1969
Posts: 906
Senior Member
OP Offline
Senior Member
Joined: Dec 1969
Posts: 906
Well spotted. I'm still slightly mystified as to how this happened; as I mentioned, the compiler settings haven't changed in several releases. But whatever, I guess I can do a G4 friendly compile now... given that the release has been out for a while I'd rather wait for v2.0.1 now though. Any other bugs?

Joined: Mar 2001
Posts: 16,613
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,613
I can drop in the improved YM2612 emulation for VGM/GYM files if you want an excuse.

Joined: May 2006
Posts: 111
Senior Member
Offline
Senior Member
Joined: May 2006
Posts: 111
That would be really cool.

Honestly, I'd really like to see the SPC issue fixed in the Macintosh build. You know, the one cutting songs short when checking the "pre-calculate volumes" box. Also, AO seems to be unable to determine the duration of SPC files, because the information bar doesn't display it. Furthermore you cannot record SPCs for a longer duration than their original length determined in the ID666 tags.

By the way, is there any way to display the song titles in the playlist instead of the file names?


Other than that, I've noticed a few broken songs in Final Fantasy XII (already present in older releases) and the inability of the Linux version to open multiple files (I think I already reported that one).

Last edited by F-3582; 08/07/08 10:34 PM.
Joined: Mar 2001
Posts: 16,613
R
Very Senior Member
Offline
Very Senior Member
R
Joined: Mar 2001
Posts: 16,613
Uhh, the Linux version opens multiple files fine here, in every sense of those words I can think of. Open is multi-select enabled in 2.0, and there's certainly no problem having large playlists.

Joined: May 2006
Posts: 111
Senior Member
Offline
Senior Member
Joined: May 2006
Posts: 111
...I should probably have tested the new Linux version before posting. Never mind, then.

Page 3 of 10 1 2 3 4 5 9 10

Moderated by  R. Belmont, Richard Bannister 

Link Copied to Clipboard
Who's Online Now
6 members (Mr. Do, judge, Duke, RColtrane, 2 invisible), 31 guests, and 3 robots.
Key: Admin, Global Mod, Mod
ShoutChat
Comment Guidelines: Do post respectful and insightful comments. Don't flame, hate, spam.
Forum Statistics
Forums9
Topics8,836
Posts116,223
Members4,921
Most Online890
Jan 17th, 2020
Powered by UBB.threads™ PHP Forum Software 7.7.5