From grass-lists-owner@max.cecer.army.mil Mon Jan 31 15:48:44 1994
Date: Mon, 31 Jan 94 13:57:38 EST
From: ld+0075!dotson@uu5.psi.com (Doug Dotson)
Sender: grass-lists-owner@max.cecer.army.mil
Reply-To: grassu-list@max.cecer.army.mil
To: grassu-list@max.cecer.army.mil
Subject: Re: Help with XKeysymDB file
Content-Length: 544I had a similar experiance when I downloaded the binaries. I never did figure
out why it happened and several from this list offered suggestion of which
none worked. For other reasons I downloaded the source and did a complete
rebuild including XGRASS. The problem went away. This suggestes that the
keysym table is compiled into the code. I was not under the impression that
this was the case, I thought the it was dynamically loaded at runtime. I
never persued it further since my purposes were satisfied.Doug Dotson
dotson@tate.com
This is similar to our experiance. The messages that I posted about two
weeks ago were for the binaries (of xdigit) that we downloaded from CERL.
We have since recompiled xdigit, with update 3 installed, and the XKeysymDB
warnings came back. Using the strings command that I posted the note about
before showed two things:
%s/lib/XKeysymDB
/usr/openwin/lib/XKeysymDB
I then appended the motif XKeysymDB file to the /usr/openwin/lib/XKeysymDB
file and the warnings went away. I did not have time to find where the
%s/lib/XKeysymDB message came from; more pressing things popped up.
Ken Sibley
USDA-SCS
ksibley@ncg.scs.ag.gov