[comp.windows.x] Help with MOTIF on Suns

bob@odi.COM (Bob Miner) (09/09/89)

>     Has anyone out there gotten Motif to run on a Sun machine of any
>     flavor? 

Yes.  I've gotten both snapshot 11 and release 1.0 running on Sun3's,
SunOS 4.0.3 with the Sun cc compiler with minimal effort.  Below are
what I would recommend you do to build Motif 1.0 (I can't speak for
earlier releases, but why would you want to build them anyways?):

* First, read the porting guide in one of the ./doc/releasePorting
  directories.

* Look at the file ./util/imake.includes/Sun.macros and make sure that
  the OS version is correct.  Look around to see if anything else should
  be changed for your particular situation.

* Go to the top motif directory and follow the instructions on page 4
  of the releasePorting documentation.  Basically this amounts to
  doing a 'make Makefile' to make ./Makefile, doing a 'make Makefiles'
  to make all the Makefiles in lower directories, doing a 'make depend'
  to add dependencies to your Makefiles and then doing a 'make' to actually
  do the build.  You may also want to remove TESTSRC\ from DIRSTOMAKE in
  the top level Makefile if you want to avoid 200+ Mb of testing stuff.
  I did.

* Once the make is finished, you probably had some errors.  Errors that
  I encountered and fixed were:

    - Mrmtime.c includes time.h.  It doesn't need to as it's also
      included in Xos.h, so just remove it and remake.  I sent a bug
      report in on this one.

    - WmResource.c has the default function key bindings, one of
      which, maximize, binds F10.  My Sun3 keyboard doesn't have an F10,
      so I changed it to F6.  This isn't a bug.

    - Some of the demo programs wouldn't build because they included
      limits.h.  Just remove that include and rebuild and they'll work fine.
      Someone else has sent a bug report in on this one.

That's it.  As I said, not that complex.  I didn't do a make install because I
didn't want to overwrite existing X11R3 includes and libraries.  Instead, I
manually moved includes to /usr/include/Xmotif/{X11,Xm,Mrm} directories.  So
when compiling with Motif, I specify -I/usr/include/Xmotif to get Motif
include files before X11R3 versions.  I also moved the Motif libXt.a to
/usr/lib/libXtm.a, so I can link against either the Motif intrinsics or the
X11R3 intrinsics.  If Motif 1.1 uses the vanilla X11R4 intrinsics, the
need to keep two versions of the intrinsics will disappear then.

If you don't do a make install, you'll also need to do a 'build.docs longnames'
to expand the names of man page files to their longer names.

Good Luck,

Bob Miner
					    Object Design Inc.
Internet: bob@odi.com			    1 New England Executive Park
Or: odi!bob@uunet.uu.net		    Burlington, MA 01803
Or: odi!bob@eddie.mit.edu		    (617) 270-9797

mack@inco.UUCP (Dave Mack) (09/12/89)

In article <5534@inco.UUCP> I wrote:
>
>Has anyone out there gotten Motif to run on a Sun machine of any
>flavor? I've tried to get snapshot 4 running on a 386i under OS4.0.1
>and a Sun-2/170 under OS3.4, and mwm dies horribly every time. The
>problem (at least on the Sun-2, dbx seems to be broken on the 386i)
>appears to be in lib/Xm/XmString.c, which contains some very
>unportable code. This is typical:

OK, the only excuse I can offer is that insanity runs in my family.
Snapshot 4 is way, way out of date (I wasn't aware of this), and
the current release of Motif appears to run on Suns with no problems.

On to other news.

I just received a phone call from a very nice gentleman at OSF,
explaining that the code chunk I posted as an example of the
sort of thing that was killing mwm is Copyrighted, and that,
while OSF is not suing me, I will be getting a letter from
their lawyers. He was most apologetic about this, but OSF is
apparently extremely concerned about the possibility of Motif
accidentally slipping into the public domain.

The moral of the story, boys and girls, is that even a tiny chunk
of copyrighted software is copyrighted. I hate to think what would have 
happened if I'd posted the patch to fix the "problem".

Anyway, mea culpa, mea maxima culpa.

Let's be careful out there.

-- 
Dave Mack