Ok, I think I found it, there were lots of 32-bit .x%x.c patterns in the magicglass/nlet highlighting code, I replaced them with proper .x %lx.c patterns which should support 64-bit fine. Try tomorrow's build and let me know.

.hc

On Jul 8, 2011, at 11:37 AM, James Dunn wrote:

Sure. I did exactly what I did last time and here's the console output:

------------------ done with main ----------------------
::tk::mac::OpenApplication ++++++++++++Connection from 'pd' to 'pd- gui' on 127.0.0.1:54515
Default font: Andale Mono
libdir loader 1.9
   compiled on Jul  8 2011 at 10:30:07
   compiled against Pd version 0.43.1.extended-20110708
libdir_loader: added 'vanilla' to the global objectclass path
libdir_loader: added 'extra' to the global objectclass path
/Applications/Pd-0.43.1-extended-20110708.app/Contents/Resources/ Scripts/../extra/Gem/Gem.pd_darwin: dlopen(/Applications/Pd-0.43.1- extended-20110708.app/Contents/Resources/Scripts/../extra/Gem/ Gem.pd_darwin, 10): Symbol not found: __Z10initGemWinv Referenced from: /Applications/Pd-0.43.1-extended-20110708.app/ Contents/Resources/Scripts/../extra/Gem/Gem.pd_darwin
 Expected in: dynamic lookup

Gem: can't load library
libdir_loader: added 'cyclone' to the global objectclass path
libdir_loader: added 'zexy' to the global objectclass path
The Pd window filtered 13 lines
(Tcl) INVALID COMMAND NAME: invalid command name ".x1634dc0.c"
   while executing
".x1634dc0.c itemconfigure .x101634dc0.t101635200o0 -outline $select_color -width 3"
   ("uplevel" body line 1)
   invoked from within
"uplevel #0 $cmd_from_pd"(Tcl) INVALID COMMAND NAME: invalid command name ".x1634dc0.c"
   while executing
".x1634dc0.c itemconfigure .x101634dc0.t101635200o0 -outline $signal_cord -fill $signal_nlet -width 1"
   ("uplevel" body line 1)
   invoked from within
"uplevel #0 $cmd_from_pd"

Quoth Hans-Christoph Steiner, on 07/07/2011 16:29:
I guess I need to find me a 10.6 machine to debug on... could you do me a favor and try running that debug session again, then in the Pd window, switch the log to 'debug', and copy and paste the contents in an email
reply to this thread?

.hc

On Thu, 07 Jul 2011 11:27 +0100, "James Dunn"<[email protected]>
wrote:
I thought I'd try and install the latest pd extended on my Macbook Pro (10.6.8, 2.7GHz Intel Core i7, 64bit) but I get a lot of errors. This is
with the latest build of Pd-0.43.1-extended-macosx106-x86_64.dmg

I've attached a screenshot. All I did was run pd, open a new patch and add a bang object with command-shift-b. This created two objects, one which was created at the mouse position, and another following the mouse
movement. Then I created an [osc~] object and got the errors in the
console.

James

Email had 1 attachment:
+ Screen shot 2011-07-07 at 11.19.47.png
  366k (image/png)



----------------------------------------------------------------------------

"A cellphone to me is just an opportunity to be irritated wherever you are." - Linus Torvalds


_______________________________________________
[email protected] mailing list
UNSUBSCRIBE and account-management -> 
http://lists.puredata.info/listinfo/pd-list

Reply via email to