On Tue, 6 Sep 2005, Viv Kendon wrote:
On Tue, 6 Sep 2005, Jean-François Mertens wrote:
On 06 Sep 2005, at 20:42, Viv Kendon wrote:
On Tue, 6 Sep 2005, Jean-François Mertens wrote:
On 06 Sep 2005, at 19:35, Viv Kendon wrote:
On Tue, 6 Sep 2005, David R. Morrison wrote:
On Sep 6, 2005, at 9:50 AM, Viv Kendon wrote:
Hmmm, trying to run xdvi give me
dyld: Symbol not found: __XEditResCheckMessages
Referenced from: /sw/bin/xdvi-motif.bin
Expected in: /sw/lib/libXm.3.dylib
Trace/BPT trap
libXm.3.dylib is from openmotif3-shlibs-2.2.3-11.
Drat: rebuild of openmotif3 complete, still same error running xdvi.
Looking back, your first guess (and Dave's reply) were completely correct.
My xdvi-motif.bin takes __XEditResCheckMessages from (xorg's) /usr/
X11R6/lib/libXmu.6.dylib
OK, I am compiling tetex-base from source...I expect it will be tomorrow (my
local time) before I can report whether this works.
Tetex-base compiled much quicker than I thought...xdvi now
basically works, but I managed to get a spectacular crash
out of it by doing something I don't normally do (navigating
to subdirs and switching files from the File-open menu).
It produces more than 1000 lines of output into the xterm
that launched it, the last few look like:
for font "xyeubt11" on line 1336 overrides previous entry.
xdvi-motif.bin: Info:
/sw/var/lib/texmf/fonts/map/dvips/updmap/ps2pk.map: Entry
for font "xyeubt12" on line 1337 overrides previous entry.
xdvi-motif.bin: Info:
/sw/var/lib/texmf/fonts/map/dvips/updmap/ps2pk.map: Entry
for font "zd" on line 1338 overrides previous entry.
************************************************************
XDvi 22.84.9 (Motif toolkit): Failed assertion:
special.c:2123: "bg_current != NULL": Background color not
initialized
Aborting now. Please report this as a bug to:
http://sourceforge.net/tracker/?group_id=23164&atid=377580
If a core dump has been produced, please invoke:
gdb xdvi-motif.bin core
Then type "bt", and include the resulting output in your bug
report.
************************************************************
Abort trap
I don't think I do have a core dump (at least I can't find
one in the obvious places like the dir I ran it from, or
~/Library/Logs/CrashReporter).
The file it crashed on probably isn't special, I can view it
OK if I open it first rather than second. And I can
reproduce it on other *.dvi files I already have. To try to
reproduce this, do the following
1. move any ~/.xdvirc out of the way
2. launch xdvi from your home dir
3. navigate to a subdir with more than one *.dvi file in
4. open one of the *.dvi files
5. select File-open from the menus
6. open a different *.dvi file
This is the point where I get the crash.
I do have extra font stuff installed via fink:
i applesystemfonts 1.1-1 Make Apple system
fonts available to X11R6
i ec-fonts-mftraced 1.0.12-2 Sauter EC
PostScript Type1 Fonts
i fc-ghostscript-fonts 20050601-1 Add
ghostscript fonts to fontconfig search
i fontconfig-path 20050601-1 Add custom
directories to fontconfig search
i fontconfig2-dev 2.2.3-10 Fontconfig 2 for
Gimp
i fontconfig2-shlibs 2.2.3-10 Fontconfig
2, shared libs
i fontforge 20050809-1 Outline font editor
i ghostscript-fonts 8.11-2 Standard fonts for
Ghostscript
i gimp-freefonts 0.10-2 Freeware scalable X11 fonts
i gimp-sharefonts 0.10-2 Shareware scalable X11 fonts
i latex-xft-fonts 0.1-11 TTF math fonts for lyx and
latex
i msttcorefonts 1.2-12 Microsoft's TrueType core
fonts for the web
i ttfmkfontdir 1.0-2 Make fonts.dir for TrueType
Fonts
i x-ghostscript-fonts 20020206-3 Allows
ghostscript fonts to be used within X-windows
i xfontpath 0.4-12 X font path manager for fink
i xfonts-intl 1.2.1-1 International Fonts
I expect I can avoid triggering this crash too often, but
the font errors seem to occur sometimes without the crash,
depending on which *.dvi file I open.
-- Viv
------------------------------------------------
Dr Viv Kendon [EMAIL PROTECTED]
Quantum Information tel: 0113 343 3858
Physics & Astronomy University of Leeds
http://quantum.leeds.ac.uk/~viv
