Submitted by Anonymous on Wed, 08/21/2002 - 01:57.
Hi,
I am trying to get a working copy of Motif running on m MacOS X systems.
-When I download the binary package (which installs using the MacOS X tools), it installs library files with mispointed symbolic links.
When I fix the links, I get this error message
Warning Fatal Error
_XmGetDefaultDisplay cannot be used prior to VendorS.Initialize, returns NULL
Warning Urm__OpenHierarchy Display not yet opened - Invalid URM code
Error can`t open hierarchy
-When I try to recompile, I get the errors about about "-undefined none" required with two-level namespace. When I add "-undefined none" to the link, I get these errors when I try to run mwm
mwm attempt to add non-widget child "dsm" to parent "mwm" which supports only widgets
-I saw something about needing to relink everything with "-flat_namespace". I just did that and I still get the same error.
I am not sure how to modify these ./configure and libtool things to add the -flat_namespace to the right commands (you know, in the good old days, we just changed the LDFLAGS line in the Makefile) so I did the link manually. For some reason, I still get the same warnings about duplicate symbols
[...]
/usr/X11R6/lib/libXp.dylib(AuRead.o) definition of _XauReadAuth
/usr/bin/ld warning suggest use of -bind_at_load, as lazy binding may result in errors or different symbols being used
symbol _XauDisposeAuth used from dynamic library /usr/X11R6/lib/libX11.dylib(AuDispose.o) not from earlier dynamic library /usr/X11R6/lib/libXp.6.dylib(AuDispose.o)
[...]
-I would really like to get Motif up and running on my MacOS X/XFree86 systems. I need a decent window manager, and I want to compile Nedit and my other Motif friends, too.
-This is on a MacOS X 10.1.4 system. I am using the December 2001 Apple Developer Tools. I have XDarwin 1.1 (XFree86 4.2.0) installed.
Wed, 08/21/2002 - 17:49#1
Anonymous
Can not get Motif on MacOS X
I`ve been waiting most of this year for someone somewhere to sort out the problems with Motif and Motif clone libraries on Mac OS X. I`m hoping that there will be a compiler and linker update with the Jaguar OS release that will allow the Motif code to be built without issues.
My primary concern is building Motif applications in my own open source project (www.ldeo.columbia.edu/MB-System)
In the meantime, here is my experience on MacOS X
1) I cannot successfully build OpenMotif myself
2) The OpenMotif binary distributions I`ve found for Mac OS X all fail to run, apparently because of conflicts between Xm and Xt functions of the same name (this is only a problem because of problems with Apples linker).
3) I cannot successfully build LessTif myself.
4) I`ve found one binary distribution of the LessTif library that mostly works when linked using the -force_flat_namespace flag. This is the fink Lesstif distribution. All of my Motif programs will compile, link and run, but one of the programs never displays its window.
Please let me know it you learn of any solutions.
Thanks,
Dave Caress
Mon, 08/26/2002 - 05:09#2
Anonymous
Can not get Motif on MacOS X
I was finally able to compile MWM on MacOS X (10.1.4). It seems the magic trick is that every Motif executable must be linked with "-force_flat_namespace". In the past, I was trying "-flat_namespace" but this is apparently different. Also note that shared libraries can`t be linked with "-force_flat_namespace" -- Apple`s libtool doesn`t accept it.
I added the "-force_flat_namespace" to the LDFLAGS line of the MWM makefile and the resulting mwm executable worked. It might be possible to add this to the global LDFLAGS but I am not sure if that would interfere with shared library creation.
I can never figure this configure/libtool stuff out. Every time I want something to propagate, it is overridden somewhere else and every time I want a localized change, it seems to affect every other file. UNIX used to be simple...
Sun, 10/06/2002 - 12:58#3
Anonymous
Can not get Motif on MacOS X
I have had motif up and compiling on OS X for about 9 months now. You can get it via fink. http//fink.sf.net/
I reccomend using the fink version. But if you don`t want to use fink you can look at my compile options and settings in Fink CVS
http//cvs.sourceforge.net/cgi-bin/viewcvs.cgi/fink/dists/10.2/unstable/main/finkinfo/x11/
look at the openmotif .info and .patch files. See fink packaging manual to decipher it.