No, its a Macbook Pro with Intel Core i7, 64 bit. System Profiler says this, in case that helps:
Processor Name: Intel Core i7
...
Boot ROM Version: MBP81.0047.B27
SMC Version (system): 1.69f3
I do have the option to run Terminal in 32 bit mode (which I have never done) by setting a checkbox in Get Info window for the Terminal app. Just looked now to be certain and its not checked, its never been running in 32 bit mode.
This is what Terminal says when I do a uname:
MacBook-Pro:Resources games$ uname -a
Darwin MacBook-Pro.local 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun 7 16:32:41 PDT 2011; root:xnu-1504.15.3~1/RELEASE_X86_64 x86_64
To be honest I am not knowledgeable enough to know the cause of my mod installation errors...it may be Weidu, or not. The process worked fine in BG-EE several months ago but now does not work there either, after I purchased BGII-EE, upgraded to the most recent BG-EE patch, and then upgraded both WEIDU (to Mac v235) and my Mac Mod Installer script (to v2.1). But the Mod Installer script is pretty straightforward and seems to work as before, creating the aliases to dialog.tlk etc, finding Weidu, then running Terminal and calling the setup file in Terminal. But then Terminal goes splat. Terminal also goes splat in similar ways if I click on the .command file for a mod. Like this:
MacBook-Pro:~ games$ /Applications/Baldur\'s\ Gate\ -\ Enhanced\ Edition/Game\ Data/00777/Baldur\'s\ Gate\ -\ Enhanced\ Edition.app/Contents/Resources/setup-bg2_tweaks.command ; exit;
/Applications/Baldur's Gate - Enhanced Edition/Game Data/00777/Baldur's Gate - Enhanced Edition.app/Contents/Resources/setup-bg2_tweaks.command: line 3: 1224 Illegal instruction ./setup-bg2_tweaks
logout
[Process completed]