[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-gnubg] New gnubg build problem

From: Misja Alma
Subject: [Bug-gnubg] New gnubg build problem
Date: Thu, 23 Aug 2007 15:09:59 +0200

Hi All,

I have tried to build gnubg again, this time on a new computer.
I have downloaded the latest snapshot, and again on this computer the OS is Ubuntu 7.04. Only this time it is the 64 bit version.

I have followed the instructions which Nardy gave to me last time and which worked at that time.
Building and compiling seemed to go without any problems, until I tried to start gnubg by typing ./gnubg in my gnubg directory.
There were a couple of error messages, and all of them seemed to indicate the gnubg tried to find files in the /usr/local/share/gnubg directory. That's not were I installed gnubg, the same as last time I installed it in /home/misja/gnubg. Anyway, below is the complete error message. Could anybody please help?


Python supported.
Window system supported.
External players supported.
XML match equity files supported.
External commands supported.
ESD sound system supported.
Multiple threads supported.
SSE supported and available.

(gnubg:21849): Gtk-WARNING **: Error loading icon from file '/usr/local/share/gnubg/gnubg.png':
        Failed to open file '/usr/local/share/gnubg/gnubg.png': No such file or directory
I/O warning : failed to load external entity "/usr/local/share/gnubg/usr/local/share/gnubg/met/g11.xml"
Error reading XML file (/usr/local/share/gnubg/met/g11.xml): not well-formed!

(gnubg:21849): Gtk-CRITICAL **: gtk_main_quit: assertion `main_loops != NULL' failed


Note that gnubg does not use the gnubg.bd file.
You should obtain the file gnubg_ts0.bd or generate
it yourself using the program 'makebearoff'.
You can generate the file with the command:
makebearoff -t 6x6 -f gnubg_ts0.bd
You can also generate other bearoff databases; see
README for more details

/usr/local/share/gnubg/gnubg.wd/usr/local/share/gnubg/gnubg.weights(No game) Segmentation fault (core dumped)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]