Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#16794 closed defect (fixed)

wxMaxima 0.7.5 not supported on the architecture

Reported by: carlonluca (Luca Carlon) Owned by: usami-k@…
Priority: Normal Milestone:
Component: ports Version: 1.6.0
Keywords: Cc: jmroot (Joshua Root)
Port: wxMaxima

Description

I compiled three times wxMaxima but when I try to run it I get:

"You cannot open the application “wxMaxima.app” because it is not supported on this architecture."

0.7.3a used to work.

Change History (21)

comment:1 Changed 16 years ago by jmroot (Joshua Root)

Cc: jmr@… added
Owner: changed from macports-tickets@… to usami-k@…
Port: wxMaxima added

comment:2 in reply to:  description Changed 16 years ago by usami-k@…

On my environment, wxMaxima 0.7.5 works fine.

  • Case 1 : Mac OS X 10.4.11, PowerPC, Xcode 2.5
  • Case 2 : Mac OS X 10.5.5, Intel, Xcode 3.1.1

comment:3 Changed 16 years ago by carlonluca (Luca Carlon)

Still fails to run on Mac OS X 10.5.5, Intel, Xcode 3.1.1. Is there any way to find out what's wrong?

comment:4 Changed 16 years ago by jmroot (Joshua Root)

What does file /Applications/MacPorts/wxMaxima.app/Contents/MacOS/wxmaxima report?

comment:5 Changed 16 years ago by carlonluca (Luca Carlon)

This is the output:

/Applications/MacPorts/wxMaxima.app/Contents/MacOS/wxmaxima: Mach-O executable i386

comment:6 Changed 16 years ago by carlonluca (Luca Carlon)

Running maxima from that file inside the package seems to work more or less. It's not completely ok as it can't find some files but it works.

comment:7 in reply to:  6 Changed 16 years ago by blb@…

Replying to carlon.luca@…:

Running maxima from that file inside the package seems to work more or less. It's not completely ok as it can't find some files but it works.

What files aren't being found, maybe those would be a clue as to why running it as a .app isn't working?

comment:8 Changed 16 years ago by carlonluca (Luca Carlon)

During the startup the app signals the tip files are missing, and this is the log file of the other missing files:

23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/open.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/save.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/print.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/configure.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/copy.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/cut.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/text.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/input.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/stop.png': file does not exist.
23:27:23: Can't load image from file 'wxMaxima.app/Contents/Resources/toolbar/help.png': file does not exist.

I see those files are in the package in the correct position, maybe that's because the relative path is not correct related to the position of the executed file?

comment:9 Changed 16 years ago by blb@…

Yeah, those are apparently assuming a specific location when being run (/Applications/MacPorts); when you try to launch the .app via Finder, do you see anything in the system or console logs (open /Applications/Utilities/Console to see)?

comment:10 Changed 16 years ago by carlonluca (Luca Carlon)

Nothing is written on the console when trying to launch wxMaxima.app. This is what I get instead when I launch the app from the wxMaxima executable:

11/17/08 9:43:53 AM wxmaxima[220] NSDocumentController Info.plist warning: The values of CFBundleTypeRole entries must be
'Editor', 'Viewer', 'None', or 'Shell'. 

I don't know if it's useful. Anyway, I've been able to make the .app working a few times. If I uninstall it and then I install it again, I get a not working .app. If I use the wxMaxima executable, I reboot the system and I use the executable again, then I have a working .app. If again I uninstall it and install it again, the icon of wxMaxima has the forbidden signal on it and launching it results in the message of architecture not supported. Again following the steps I reported it starts to work perfectly. I don't really now why, does this mean anything to you? Thanks!

comment:11 Changed 16 years ago by blb@…

Definitely very odd; that NSDocumentController message is just a warning as the app doesn't set CFBundleTypeRole for the wxm file extension.

If you (in Finder) do a Get Info on the app itself, does it at least show you have read-only access?

comment:12 Changed 16 years ago by carlonluca (Luca Carlon)

In Get Info I see system is Read & Write, admin is Read only and everyone is Read only. The same permissions when the app is working and when it's not.

comment:13 Changed 16 years ago by blb@…

I'm stumped; though I do see 0.7.6 was released a few months ago, perhaps that may help if an older version was working...

comment:14 Changed 16 years ago by carlonluca (Luca Carlon)

Yes, in fact I was about to ask you if it made sense to fix this. Anyway, I've got another information for you: I tried to run wxmaxima from a terminal and it seems it works, and it doesn't show any error message about missing files of any kind, no complains. How can it be different running the executable from finder rather than launching it from the terminal?

comment:15 Changed 16 years ago by carlonluca (Luca Carlon)

Ok, I had this suspect yesterday, but I know nothing about .app files. I suspect the name of the executable file is supposed to be the same as the name of the .app. Is this correct? I noticed the name of the app is wxMaxima whereas the executable is named wxmaxima... and my filesystem is case sensitive. I just tried to install the app again so that it doesn't work and then I did a:

sudo mv wxmaxima wxMaxima

The .app suddenly changed its icon and worked like a charm. This would explain why someone has the .app working right after the installation.

comment:16 Changed 16 years ago by blb@…

Actually, the name of the executable in Contents/MacOS doesn't have to match the app name, but it does have to match what's in Info.plist for the CFBundleExecutable key; this key is currently wxMaxima hence your problem on a case-sensitive filesystem.

Either the executable in Contents/MacOS can be renamed as you did, or the value for CFBundleExecutable can be updated to wxmaxima, should fix it.

What says the maintainer?

comment:17 Changed 16 years ago by usami-k@…

OK. I fix CFBundleExecutable key. (Ticket #17340)

Thank you for pointing out.

comment:18 Changed 16 years ago by mf2k (Frank Schima)

Fix applied in r42440. Does it work for you now?

comment:19 Changed 16 years ago by carlonluca (Luca Carlon)

Yes, seems to work, thanks!

comment:20 Changed 16 years ago by mf2k (Frank Schima)

Resolution: fixed
Status: newclosed

comment:21 Changed 16 years ago by (none)

Milestone: Port Bugs

Milestone Port Bugs deleted

Note: See TracTickets for help on using tickets.