home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!agate!dog.ee.lbl.gov!epb11.lbl.gov!envbvs
- From: envbvs@epb11.lbl.gov (Brian V. Smith)
- Newsgroups: comp.windows.x
- Subject: Re: Missing externals making xfig
- Date: 22 Jan 1993 17:47:54 GMT
- Organization: lbl
- Lines: 48
- Distribution: world
- Message-ID: <28579@dog.ee.lbl.gov>
- References: <9301220006.AA00220@usppc.abb.com>
- NNTP-Posting-Host: 128.3.12.123
-
-
- |> I'm trying to make xfig from the X-11R4 contributed clients. It went
- |> well to make a couple of minor fixes to compound object pointer
- |> declarations. Then the fun began. I use the enclosed Imakefile to get
- |> something which does this come ld time. The Makefile does the following
- |> to link the program
- |>
-
- |>
- |> This gives two undefined entry points:
- |>
- |> ld: Undefined symbol
- |> _get_wmShellWidgetClass
- |> _get_applicationShellWidgetClass
-
- First, you should get the latest version from export.lcs.mit.edu in
- /contrib/R5fixes/xfig-patches/xfig.2.1.6.tar.Z and the fig to printer
- translator, transfig from
- /contrib/R5fixes/transfig-patches/transfig.2.1.6.tar.Z.
-
- Then, please check the FAQ:
-
- ----------------------------------------------------------------------
-
- Subject: 96)! What is this strange problem building X clients on SunOS 4.1.2?
-
- In SunOS 4.1.2 Sun fixed a shared-library bug in ld which conflicts
- with the way X11R4 builds the shared Xmu library, causing these symbols to be
- undefined when building some X11 clients:
- _get_wmShellWidgetClass
- _get_applicationShellWidgetClass
- Compiling "-Bstatic -lXmu -Bdynamic" appears to work.
-
- To solve the problem if you are using OpenWindows 3.0 (X11R4-based Xt), please
- contact your local Sun office and request the following patches:
-
- Patch i.d. Description
- 100512-02 4.1.x OpenWindows 3.0 libXt Jumbo patch
- 100573-03 4.1.x OpenWindows 3.0 undefined symbols when using
- shared libXmu
- ----------------------------------------------------------------------
-
- You CAN safely use it, though.
-
- --
- Brian V. Smith (bvsmith@lbl.gov)
- Lawrence Berkeley Laboratory
- I don't speak for LBL; they don't pay me enough for that.
-