[MacPorts] #1936: BUG: devel/mono doesn't look in /opt/local/lib at runtime
MacPorts
noreply at macports.org
Wed Dec 15 13:48:27 PST 2010
#1936: BUG: devel/mono doesn't look in /opt/local/lib at runtime
-----------------------------------+----------------------------------------
Reporter: chris.ridd@… | Owner: mww@…
Type: defect | Status: reopened
Priority: Normal | Milestone:
Component: ports | Version: 1.0
Resolution: | Keywords:
Port: mono |
-----------------------------------+----------------------------------------
Comment(by chris@…):
Replying to [comment:25 ionic@…]:
> Is this still a problem for anyone?
>
I'm running into the missing GdipCreateFromContext_macosx, on OS/X 10.4
and 10.5, even a single form with a textbox and a button will crash almost
immediately after launch. My symptoms are the same as is mentioned in
this ticket.
On 10.4 it actually takes longer to crash, and doesn't render any elements
inside the windows - though the windows are visible albeit blank ones.
Using MessageBox.Show produces a blank (but seemingly correctly sized)
window as well.
The steps I took were this:
- Have mono tools for visual studio installed on networked windows
machine (windows 7, x64).
- Have a x86 project created and ready to debug/execute.
- Install macports for Tiger (or Leopard, depending on OS version) on
networked OS/X machine.
- Run the macports selfupdate, then port install mono and gtk-sharp2
- Install the mono tools server for OS/X.
- Note: On the 10.4 machine, I actually rebuilt mono tools server from
source and all that remedied was the crashes I was encountering when doing
'Debug in mono' rather than 'Run in mono' from visual studio. Visual
studio is what crashed in that case.
- Perform a 'Run in mono' from visual studio with the OS/X machine as the
target for the session.
Result:
- The window appears for a split second on 10.5, and then disappears
with the crash report starting off with the missing
GdipCreateFromContext_macosx
- The window appears and stays open for some time on 10.4, but as soon
as the window is clicked or minimized or anything the application crashes
with the same error. Waiting for about 20-30 seconds will also cause it
to crash, but it seems to crash faster if I try to do something with the
windows that had shown up.
If there's a known fix to get past this I'd like to know what it is. This
seems like a major roadblock for distributing applications intended for
multiple platforms using mono; it doesn't seem as though it even works.
I am going to attempt to find alternate sources of mono, in case this is
issue is specific to macports and will report here if that proves
fruitful.
--
Ticket URL: <https://trac.macports.org/ticket/1936#comment:27>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list