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

[Eli Dayan]

Hi All, I am pretty certain that last time I built gnubg here on 
FreeBSD, clang/llvm was used. I upgraded gcc to gcc4.9 from ports last 
night and tried to build with this with Philippe's suggested 
optimisations. 4ply was a little slow so I thought I could speed things 
up a bit. Here is what happens when I run configure: checking build 
system type... amd64-unknown-freebsd10.0 checking host system type... 
amd64-unknown-freebsd10.0 checking for a BSD-compatible install... 
/usr/bin/install -c checking whether build environment is sane... yes 
checking for a thread-safe mkdir -p... ./install-sh -c -d checking for 
gawk... no checking for mawk... no checking for nawk... nawk checking 
whether make sets $(MAKE)... yes checking whether make supports nested 
variables... yes checking for host... amd64-unknown-freebsd10.0 checking 
for style of include used by make... GNU checking for gcc... gcc49 
checking whether the C compiler works... no configure: error: in 
`/usr/home/eli/gnubg': configure: error: C compiler cannot create 
executables See `config.log' for more details I tried setting CC to 
gcc49, then running configure and that's what I get. % CC=gcc49 
CPPFLAGS="-O3 -funroll-loops -march=native -mtune=native 
--enable-simd=avx" ./configure I tested gcc4.9 slightly by building your 
favourite hello world program, and it works just fine. What am I doing 
wrong? Thanks for the help, and I appologise for my simple questions -- 
I'm usually good on UNIX systems Thanks guys. Eli Dayan On 02/11/14 
16:02, Philippe Michel wrote: > 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. > > 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.