Re: [Computer-go] Strange GNU Go ladder behavior
(Apologies if there's something in the output I should be able to
understand; my sysadmin skills are weak.)
Configure doesn't seem happy with that:
[drake@broadcast gnugo-3.8]$ ./configure --build=i686-pc-linux-gnu
CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name...
configure: error: C compiler cannot create executables
See `config.log' for more details.
Here's config.log:
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.
It was created by gnugo configure 3.8, which was
generated by GNU Autoconf 2.61. Invocation command line was
$ ./configure --build=i686-pc-linux-gnu CFLAGS=-m32 CXXFLAGS=-m32
LDFLAGS=-m32
## - ##
## Platform. ##
## - ##
hostname = broadcast
uname -m = x86_64
uname -r = 3.10.0-229.4.2.el7.x86_64
uname -s = Linux
uname -v = #1 SMP Wed May 13 10:06:09 UTC 2015
/usr/bin/uname -p = x86_64
/bin/uname -X = unknown
/bin/arch = x86_64
/usr/bin/arch -k = unknown
/usr/convex/getsysinfo = unknown
/usr/bin/hostinfo = unknown
/bin/machine = unknown
/usr/bin/oslevel = unknown
/bin/universe = unknown
PATH: /sbin
PATH: /bin
PATH: /usr/sbin
PATH: /usr/bin
## --- ##
## Core tests. ##
## --- ##
configure:1841: checking for a BSD-compatible install
configure:1897: result: /bin/install -c
configure:1908: checking whether build environment is sane
configure:1951: result: yes
configure:2016: checking for gawk
configure:2032: found /bin/gawk
configure:2043: result: gawk
configure:2054: checking whether make sets $(MAKE)
configure:2075: result: yes
configure:2265: checking whether to enable maintainer-specific portions of
Makefiles
configure:2274: result: no
configure:2467: checking for gcc
configure:2483: found /bin/gcc
configure:2494: result: gcc
configure:2732: checking for C compiler version
configure:2739: gcc --version 5
gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9)
Copyright (C) 2013 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
configure:2742: $? = 0
configure:2749: gcc -v 5
Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-redhat-linux/4.8.3/lto-wrapper
Target: x86_64-redhat-linux
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
--infodir=/usr/share/info --with-bugurl=http://bugzilla.redhat.com/bugzilla
--enable-bootstrap --enable-shared --enable-threads=posix
--enable-checking=release --with-system-zlib --enable-__cxa_atexit
--disable-libunwind-exceptions --enable-gnu-unique-object
--enable-linker-build-id --with-linker-hash-style=gnu
--enable-languages=c,c++,objc,obj-c++,java,fortran,ada,go,lto
--enable-plugin --enable-initfini-array --disable-libgcj
--with-isl=/builddir/build/BUILD/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/isl-install
--with-cloog=/builddir/build/BUILD/gcc-4.8.3-20140911/obj-x86_64-redhat-linux/cloog-install
--enable-gnu-indirect-function --with-tune=generic --with-arch_32=x86-64
--build=x86_64-redhat-linux
Thread model: posix
gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC)
configure:2752: $? = 0
configure:2759: gcc -V 5
gcc: error: unrecognized command line option '-V'
gcc: fatal error: no input files
compilation terminated.
configure:2762: $? = 4
configure:2785: checking for C compiler default output file name
configure:2812: gcc -m32 -m32 conftest.c 5
/bin/ld: cannot find crt1.o: No such file or directory
/bin/ld: cannot find crti.o: No such file or directory
/bin/ld: skipping incompatible
/usr/lib/gcc/x86_64-redhat-linux/4.8.3/libgcc_s.so when searching for
-lgcc_s
/bin/ld: cannot find -lgcc_s
/bin/ld: skipping incompatible /usr/lib64/libc.so when searching for -lc
/bin/ld: cannot find -lc
/bin/ld: skipping incompatible
/usr/lib/gcc/x86_64-redhat-linux/4.8.3/libgcc_s.so when searching for
-lgcc_s
/bin/ld: cannot find -lgcc_s
/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status
configure:2815: $? = 1
configure:2853: result:
configure: failed program was:
| /* confdefs.h. */
| #define PACKAGE_NAME gnugo
| #define PACKAGE_TARNAME gnugo
| #define PACKAGE_VERSION 3.8
| #define PACKAGE_STRING gnugo 3.8
| #define PACKAGE_BUGREPORT
| #define PACKAGE gnugo
| #define VERSION 3.8
| #define GNU_PACKAGE GNU gnugo
| /* end confdefs.h. */
|
| int
| main ()
| {
|
| ;
| return 0;
| }
configure:2860: error: C compiler cannot create executables
See `config.log' for
Re: [Computer-go] Strange GNU Go ladder behavior
It seems GNU Go built in 64bit has some problems. I got crash on 64bit, but 32bit binary on 64 bit debian was ok. Try to build 32bit binary GNU Go. $ tar xvf gnugo-3.8.tar.gz $ cd gnugo-3.8 $ ./configure --build=i686-pc-linux-gnu CFLAGS=-m32 CXXFLAGS=-m32 LDFLAGS=-m32 $ make yss@debian:~/gnugo-3.8/interface$ ./gnugo -l crashes-gnugo.sgf white (O) move J8 yss@debian:~/gnugo-3.8/interface$ gcc -v gcc version 4.7.2 (Debian 4.7.2-5) Regards, Hiroshi Yamashita - Original Message - From: Peter Drake dr...@lclark.edu To: computer-go@computer-go.org Sent: Friday, June 19, 2015 11:22 PM Subject: Re: [Computer-go] Strange GNU Go ladder behavior CentOS Linux release 7.1.1503 64 bit I'm not sure which compiler the make script invoked, but I have these installed: gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) cc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
Configure doesn't seem happy with that: I'm not familiar with CentOS, but maybe need to install # yum -y install glibc-devel.i386 libstdc++-devel.i386 or # yum -y install glibc-devel.i686 glibc-devel ibstdc++-devel.i686 Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
So what is the 64-bit problem? (Or did I misread?) On Jun 19, 2015 8:04 PM, Peter Drake dr...@lclark.edu wrote: Okay, that worked (with the correction that ibstdc should be libstdc). The new version doesn't choke on my sgf file! Now for the acid test, running the whole experiment... On Fri, Jun 19, 2015 at 4:43 PM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: Configure doesn't seem happy with that: I'm not familiar with CentOS, but maybe need to install # yum -y install glibc-devel.i386 libstdc++-devel.i386 or # yum -y install glibc-devel.i686 glibc-devel ibstdc++-devel.i686 Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
I got through the whole 640-game experiment without a crash! (The cloud is a wonder, allowing me to play 640 games in under an hour.) Many thanks to everyone for your help. One game did run very long, thanks to GNU Go. See the time left signals in the SGF: (;FF[4]CA[UTF-8]AP[Orego8]KM[7.5]GM[1]RU[Chinese]SZ[19] PB[/usr/local/bin/gnugo --boardsize 19 --mode gtp --quiet --chinese-rules --capture-all-dead --positional-superko --komi 7.5] PW[/usr/bin/java -cp /home/drake/Orego/bin/ -ea -Xmx1024M edu.lclark.orego.ui.Orego boardsize=19 komi=7.5 memory=1024 shape shape-bias=10 shape-minstones=3 shape-scaling-factor=0.999 log-file=logging] ;B[dp]BL[500] ;W[pd]WL[500] ;B[pq]BL[500] ;W[cd]WL[500] ;B[ed]BL[500] ;W[ec]WL[500] ;B[fc]BL[500] ;W[dc]WL[500] ;B[qf]BL[499] ;W[qj]WL[493] ;B[fd]BL[499] ;W[fb]WL[486] ;B[gb]BL[499] ;W[gc]WL[480] ;B[hc]BL[497] ;W[gd]WL[473] ;B[ge]BL[495] ;W[hd]WL[466] ;B[id]BL[492] ;W[he]WL[459] ;B[hf]BL[488] ;W[ie]WL[453] ;B[je]BL[480] ;W[if]WL[446] ;B[ig]BL[473] ;W[jf]WL[439] ;B[kf]BL[462] ;W[jg]WL[433] ;B[jh]BL[447] ;W[kg]WL[427] ;B[lg]BL[426] ;W[kh]WL[420] ;B[ki]BL[401] ;W[lh]WL[414] ;B[mh]BL[365] ;W[li]WL[408] ;B[lj]BL[302] ;W[mi]WL[401] ;B[ni]BL[234] ;W[mj]WL[395] ;B[mk]BL[99] ;W[nj]WL[389] ;B[oj]BL[-29] ;W[nk]WL[383] ;B[nl]BL[-190] ;W[ok]WL[377] ;B[pk]BL[-357] ;W[ol]WL[371] ;B[om]BL[-616] ;W[pl]WL[366] ;B[ql]BL[-849] ;W[pm]WL[360] ;B[pn]BL[-1231] ;W[qm]WL[354] ;B[rm]BL[-1668] ;W[qn]WL[348] ;B[qo]BL[-2149] ;W[rn]WL[343] ;B[ro]BL[-2208] ;W[sn]WL[337] ;B[so]BL[-2248] ;W[pf]WL[332] ;B[cf]BL[-2253] ;W[de]WL[326] ;B[dh]BL[-2255] ;W[cj]WL[321] ;B[ej]BL[-2257] ;W[ek]WL[316] ;B[pg]BL[-2259] ;W[qg]WL[310] ;B[qh]BL[-2267] ;W[ph]WL[305] ;B[rg]BL[-2278] ;W[eg]WL[300] ;B[df]BL[-2288] ;W[ef]WL[295] ;B[ee]BL[-2295] ;W[og]WL[290] ;B[pi]BL[-2309] ;W[qi]WL[285] ;B[oh]BL[-2318] ;W[pb]WL[280] ;B[dj]BL[-2324] ;W[di]WL[275] ;B[ci]BL[-2329] ;W[ei]WL[270] ;B[ck]BL[-2337] ;W[dk]WL[266] ;B[bj]BL[-2344] ;W[bf]WL[261] ;B[be]BL[-2348] ;W[dg]WL[256] ;B[bg]BL[-2359] ;W[cg]WL[252] ;B[af]BL[-2365] ;W[bh]WL[247] ;B[ch]BL[-2373] ;W[ag]WL[243] ;B[bf]BL[-2382] ;W[bd]WL[238] ;B[fj]BL[-2385] ;W[ae]WL[234] ;B[ad]BL[-2388] ;W[ac]WL[230] ;B[fk]BL[-2392] ;W[fl]WL[225] ;B[el]BL[-2394] ;W[ah]WL[221] ;B[ai]BL[-2398] ;W[ce]WL[217] ;B[bi]BL[-2405] ;W[bh]WL[213] ;B[gl]BL[-2409] ;W[ag]WL[209] ;B[ah]BL[-2414] ;W[gk]WL[205] ;B[fm]BL[-2419] ;W[lk]WL[201] ;B[sm]BL[-2438] ;W[dl]WL[198] ;B[bc]BL[-2441] ;W[en]WL[194] ;B[fo]BL[-2443] ;W[fn]WL[191] ;B[gn]BL[-2444] ;W[go]WL[188] ;B[fp]BL[-2446] ;W[bk]WL[184] ;B[ho]BL[-2449] ;W[gj]WL[181] ;B[pe]BL[-2451] ;W[gp]WL[178] ;B[gq]BL[-2454] ;W[hp]WL[175] ;B[io]BL[-2457] ;W[hn]WL[171] ;B[gm]BL[-2463] ;W[hl]WL[168] ;B[kl]BL[-2467] ;W[ep]WL[165] ;B[eo]BL[-2478] ;W[fq]WL[162] ;B[do]BL[-2487] ;W[em]WL[159] ;B[hq]BL[-2498] ;W[ip]WL[156] ;B[jp]BL[-2511] ;W[iq]WL[153] ;B[ir]BL[-2526] ;W[jq]WL[150] ;B[kq]BL[-2540] ;W[jr]WL[147] ;B[kr]BL[-2564] ;W[js]WL[144] ;B[ks]BL[-2583] ;RE[B+Resign] ;C[moves:155] ;C[starttime:Sat Jun 20 03:22:53 UTC 2015] ;C[endtime:Sat Jun 20 04:20:17 UTC 2015] ) On Fri, Jun 19, 2015 at 8:04 PM, Peter Drake dr...@lclark.edu wrote: Okay, that worked (with the correction that ibstdc should be libstdc). The new version doesn't choke on my sgf file! Now for the acid test, running the whole experiment... On Fri, Jun 19, 2015 at 4:43 PM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: Configure doesn't seem happy with that: I'm not familiar with CentOS, but maybe need to install # yum -y install glibc-devel.i386 libstdc++-devel.i386 or # yum -y install glibc-devel.i686 glibc-devel ibstdc++-devel.i686 Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
Okay, that worked (with the correction that ibstdc should be libstdc). The new version doesn't choke on my sgf file! Now for the acid test, running the whole experiment... On Fri, Jun 19, 2015 at 4:43 PM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: Configure doesn't seem happy with that: I'm not familiar with CentOS, but maybe need to install # yum -y install glibc-devel.i386 libstdc++-devel.i386 or # yum -y install glibc-devel.i686 glibc-devel ibstdc++-devel.i686 Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
I don't know the details, but apparently GNU Go has some subtle instabilities when compiled for 64 bits. I would guess that it has to do with the fact that in C, the sizes of primitive types are platform-dependent. On Fri, Jun 19, 2015 at 8:12 PM, uurtamo . uurt...@gmail.com wrote: So what is the 64-bit problem? (Or did I misread?) On Jun 19, 2015 8:04 PM, Peter Drake dr...@lclark.edu wrote: Okay, that worked (with the correction that ibstdc should be libstdc). The new version doesn't choke on my sgf file! Now for the acid test, running the whole experiment... On Fri, Jun 19, 2015 at 4:43 PM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: Configure doesn't seem happy with that: I'm not familiar with CentOS, but maybe need to install # yum -y install glibc-devel.i386 libstdc++-devel.i386 or # yum -y install glibc-devel.i686 glibc-devel ibstdc++-devel.i686 Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
[drake@broadcast ~]$ gnugo --infile results/2015/06/19/03:21:15.950/instance17-b1-2015-06-19-03:21:31.287.sgf Segmentation fault Your sgf is ok on theres 4 environments. It took about 1 minute though. GNU Go 3.9.1 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.8 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 Visual C++6.0, Windows XP, 32bit Result are same. yss@debian:~/gnugo-3.7.10/interface$ ./gnugo -l crashes-gnugo.sgf white (O) move J8 What kind of OS, 32bit or 64bit, and compiler makes crash? Regards Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
CentOS Linux release 7.1.1503 64 bit I'm not sure which compiler the make script invoked, but I have these installed: gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) cc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) On Fri, Jun 19, 2015 at 12:45 AM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: [drake@broadcast ~]$ gnugo --infile results/2015/06/19/03:21:15.950/instance17-b1-2015-06-19-03:21:31.287.sgf Segmentation fault Your sgf is ok on theres 4 environments. It took about 1 minute though. GNU Go 3.9.1 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.8 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 Visual C++6.0, Windows XP, 32bit Result are same. yss@debian:~/gnugo-3.7.10/interface$ ./gnugo -l crashes-gnugo.sgf white (O) move J8 What kind of OS, 32bit or 64bit, and compiler makes crash? Regards Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -- Peter Drake https://sites.google.com/a/lclark.edu/drake/ ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
Re: [Computer-go] Strange GNU Go ladder behavior
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ubunut 12.04 (64 bit) self compiled with gcc -v Using built-in specs. COLLECT_GCC=gcc COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper Target: x86_64-linux-gnu Configured with: ../src/configure -v --with-pkgversion='Ubuntu 4.8.2-19ubuntu1' - --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs - --enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr - --program-suffix=-4.8 --enable-shared --enable-linker-build-id - --libexecdir=/usr/lib --without-included-gettext - --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.8 - --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu - --enable-libstdcxx-debug --enable-libstdcxx-time=yes - --enable-gnu-unique-object --disable-libmudflap --enable-plugin - --with-system-zlib --disable-browser-plugin --enable-java-awt=gtk - --enable-gtk-cairo - --with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre - --enable-java-home - --with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 - --with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 - --with-arch-directory=amd64 - --with-ecj-jar=/usr/share/java/eclipse-ecj.jar --enable-objc-gc - --enable-multiarch --disable-werror --with-arch-32=i686 --with-abi=m64 - --with-multilib-list=m32,m64,mx32 --with-tune=generic - --enable-checking=release --build=x86_64-linux-gnu - --host=x86_64-linux-gnu --target=x86_64-linux-gnu Thread model: posix gcc version 4.8.2 (Ubuntu 4.8.2-19ubuntu1) CRASHES $gnugo --infile crashes-gnugo.sgf Speicherzugriffsfehler (Speicherabzug geschrieben) Am 19.06.2015 um 16:22 schrieb Peter Drake: CentOS Linux release 7.1.1503 64 bit I'm not sure which compiler the make script invoked, but I have these installed: gcc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) cc (GCC) 4.8.3 20140911 (Red Hat 4.8.3-9) On Fri, Jun 19, 2015 at 12:45 AM, Hiroshi Yamashita y...@bd.mbn.or.jp wrote: [drake@broadcast ~]$ gnugo --infile results/2015/06/19/03:21:15.950/instance17-b1-2015-06-19-03:21:31.287.sgf Segmentation fault Your sgf is ok on theres 4 environments. It took about 1 minute though. GNU Go 3.9.1 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.8 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 gcc 4.1.2, Debian 4.1.1-21, 32bit GNU Go 3.7.10 Visual C++6.0, Windows XP, 32bit Result are same. yss@debian:~/gnugo-3.7.10/interface$ ./gnugo -l crashes-gnugo.sgf white (O) move J8 What kind of OS, 32bit or 64bit, and compiler makes crash? Regards Hiroshi Yamashita ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go -BEGIN PGP SIGNATURE- Version: GnuPG v1 iQIcBAEBAgAGBQJVhCgQAAoJEInWdHg+Znf4XvsP/2l9y9aYaawdIXeK/3S5ygW3 bvUpOQ5ZN9ez/qg4HSRFVsekjaocEEf+KiJMFoIXVBB05WldQwTCqOU0LKRDhkk7 KhWw3ntpJNK29ACXqmADR7iEvtCh7sS3IksgZZ2GCheo9IV3SkcD/zWXsFvUKINq aGWtSUN7VSAqi9ndGlhAhaeclo1ZCaN9Sq/MA1W4Od6K2CVw5sRLNhQDOVD+1dzV AKqlXsnc49GWLSOHgRXBAlNaXcYRP/LUZ86aef1FTxhdSZOg7TwIAK7OB0c80LLo R7Cz+uj8TCoa+o2RIeomN7xYIQfK6rJyRztOW+is10M4t19ggqoO0792DcSpE+1s foAeFC3+EGF3fh8hNrnkzgF1r3GDMNrBEGzCxzAtyl8tDErRS0C8AHEW2pMAgUjN Pb/+zgTAXbaTaWMfHxeMc36u+rAjLOHqPaSityTm68mB54X1unwPy4G5mI+DOwYB 38YfIdIt13GqsaJnEzpsPRe7nauld/CrPeJV3zYcxAPl1uBu1IwEOHHuEFMzC2Sn 1uk8xJtr5EIm5mbc/JXNTYxkd8phM9iGkIthWFYZPFqTijpLFrUMwhqdPCwp7+zu nDZZRYdlIeTURmxxfNV/zsvx2sfQRhRfrtg8jHNoMF0I/XfLHn11ti59pLZhAlR4 k8SMp+guTXQ0AK8Rv1l/ =an2s -END PGP SIGNATURE- ___ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
