bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] building 1.0.2.000 on FreeBSD.......


From: Philippe Michel
Subject: Re: [Bug-gnubg] building 1.0.2.000 on FreeBSD.......
Date: Tue, 11 Feb 2014 22:02:43 +0100 (CET)
User-agent: Alpine 2.00 (BSF 1167 2008-08-23)

On Tue, 11 Feb 2014, Eli Dayan wrote:

I recently moved from Linux to FreeBSD and am trying to build gnubg 1.02.000 locally. I've followed the directions on how to build, i.e.
% ./autogen.sh
% ./configure
% make

and the following errors arise:

gnubgstock.c:116:25: error: use of undeclared identifier 'ok_16'
   GNUBG_STOCK_ACCEPT, ok_16, NULL, GTK_ICON_SIZE_MENU}, {
[...]

As Michael wrote, you need GNU make to build gnubg in FreeBSD. Even if this is not the reason for the errors above, using the system make will cause problems elsewhere.

Another possibility is that some prerequisite is missing. For instance you need the graphics/gdk-pixbuf2 port ; your error messages look like they could come from its absence.

The directions on how to build from source at gnubg.org are for Ubuntu. The prerequisites for FreeBSD are similar, but the packages name may differ slightly (they differ for other Linux distributions as well...).

Some libraries used by gnubg if available are installed in /usr/local on FreeBSD. For configure to detect them, you should use :

% ./configure CPPFLAGS="-I/usr/local/include" LDFLAGS="-L/usr/local/lib"

and in general you should look at configure's output for optional features that may be missing. For instance if you intent to use the CLI, you really want to have readline compiled in, if it isn't, install the needed port, if you want to keep a database of your results, you need sqlite, etc... On the other hand, some things like gmp are not too important.

Until very recently (about one week ago), the gnubg port in FreeBSD was badly out of date. It is now 1.02, so you may simply install this port.

On the other hand, if you want to do rollouts or 4ply analyses, compiling it yourself with a recent gcc from the ports, with stronger optimizations (-O3 -funroll-loops -march=native -mtune=native works well for me, plus --enable-simd=avx if your CPU has these instructions) may well give you something up to twice as fast as the port.



reply via email to

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