I was able to get xlog to run from the build directory by adding some links from my system directories:
export XLOG_BUILD_DIR=`pwd` (when in the CVS checkout directory) sudo ln -s $XLOG_BUILD_DIR/data /usr/local/share/xlog sudo ln -s $XLOG_BUILD_DIR/data/pixmaps $XLOG_DIR/data/pixmaps/xlog This allows xlog to find the resources it needs to run, and doesn't interfear with with the syslog installed from packages, which uses /usr/share rather than /usr/local/share. All good for now.. On Thu, Jun 16, 2011 at 9:44 AM, Paul Schulz <[email protected]> wrote: > Hi Ed, > > Thanks.. I have done this, and I had all of the required packages (as > flagged by the xlog package) already installed. > > I suspect that when I install (make install) xlog everything will get > sorted out and work, but I already have a previous version of xlog > installed. > > I'll a have more of a poke. > > Cheers, > Paul > > On Thu, Jun 16, 2011 at 2:31 AM, Ed <[email protected]> wrote: >> On 06/15/2011 10:10 AM, Paul Schulz wrote: >>> >>> Greetings, >>> >>> I've checkout the code from CVS on Ubuntu 9.10. After building it I >>> have trouble running it with the following warnings/errors. >>> ------------- >>> xlog$ ./src/xlog >>> >>> ** (xlog:13558): WARNING **: Couldn't find pixmap file: mini-clock.xpm >>> >>> ** (xlog:13558): WARNING **: Could not read dxcc table >>> >>> ** (xlog:13558): WARNING **: Could not read area table >>> >>> (xlog:13558): GLib-CRITICAL **: g_hash_table_lookup: assertion >>> `hash_table != NULL' failed >>> Segmentation fault >>> >>> ------------- >>> Some comments after a quick look through the code. >>> >>> The first WARNING comes from: >>> ./src/main.c:276 >>> The directory being searched for is '/usr/local/share/pixmaps/xlog' >>> The directory where the data is './data/pixmaps' >>> >>> Is there any way of setting the data directory relative to the current >>> directory (for development purposes?) >>> >>> The above code line is also refers to 'DATADIR', rather than >>> 'XLOG_DATADIR', which the dxcc and map search paths use. >>> >>> I suspect that the last issue is because Glib can't find the data, >>> >>> Regards, >>> Paul >>> >>> ps. Should I log bugs against these issues? >> >> >> Try this first, open a terminal :: >> >> sudo apt-get build-dep xlog >> >> Now see if it will build >> >> Ed W3NR >> > _______________________________________________ Xlog-discussion mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/xlog-discussion
