[tex-live] (o)xdvi compilation problems HPUX 10.20

[Stefan Ulrich]

Lars Madsen <daleif@imf.au.dk> writes:

> Using the newest source from CTAN (6 aug 2002) I haven't been able to
> compile TL 7 with (o)xdvi

> (BTW: what is oxdvi?)

It's the omega variant of xdvi. I guess you won't need it.


> gcc -o oxdvi.bin xdvi.o dvi-draw.o dvi-init.o events.o font-open.o
> string-utils.o my-vsnprintf.o help-window.o message-window.o statusline.o
> gf.o pk.o psdps.o psgs
>  .o psheader.o psnews.o special.o util.o vf.o sfDir.o sfDraw.o sfPath.o
> sfSelFile.o hypertex.o mime.o wwwfetch.o alloca.o dvips.o tfmload.o
>  ../../libs/libwww/libwww
>  .a ../../libs/t1lib/libt1.a ../../libs/t1lib/../type1/libtype1.a
> -L/usr/contrib/X11R6/lib -lXaw -lXmu -lXt -lSM -lICE -lX11
>  ../kpathsea/STATIC/libkpathsea.a -lm
> /usr/ccs/bin/ld: Unsatisfied symbols:
>    XShapeCombineMask (code)
>    XShapeQueryExtension (code)
> collect2: ld returned 1 exit status

> Might suggest that there is a problem in the Xaw or Xmu files.

try adding
-lXext
to the linker flags and see if this fixes things ... I'm not sure
who's to blame here: If Xaw needs the shape extension, does xdvik
need to have a configure check for it, and add it to the linker
flags?


> Alternativly what would happen if we used the xdvi that are already on our
> system together with the format files set in the shared texmf tree?

That should work, provided that the original xdvi finds the fonts
etc. in your shared texmf tree.

Best,
Stefan