To jump in …

I have a similar issue with pd where compiling explicitly i386 32 bit only still cannot load a gem binary that is 32 bit ppc & i386. I have another build of gem that is also i386 only and it doesn’t load either, but I was thinking that’s due to all the build fiddling I’ve been doing in the autotools_udpate branch. Other i386 only externals are working fine.

--------
Dan Wilcox
@danomatika
danomatika.com

robotcowboy.com

On May 3, 2016, at 4:00 AM, gem-dev-request@lists.iem.at wrote:

From: j-p k <jptrkz@gmail.com>

Subject: Re: [GEM-dev] Gem Build Errors

Date: May 3, 2016 at 2:02:01 AM MDT

Cc: gem-dev@lists.iem.at

compiled against version & running version = 0.47 (keeping everything 32 bit)

output:

/Applications/Pd-0.47-0test2.app/Contents/Resources/bin/pd: Mach-O universal binary with 2 architectures

/Applications/Pd-0.47-0test2.app/Contents/Resources/bin/pd (for architecture i386): Mach-O executable i386

/Applications/Pd-0.47-0test2.app/Contents/Resources/bin/pd (for architecture ppc7400): Mach-O executable ppc

pretty sure i got the same results with 0.45-4 but i'll try again tomorrow.  0.45-4 was working with git-Gem on another computer running osx10.6 at the point gemvertexbuffer hit the wall

_______________________________________________
GEM-dev mailing list
GEM-dev@lists.iem.at
https://lists.puredata.info/listinfo/gem-dev