Re: [gnugo-devel] gnu go for ArmLinux

[brian lee dae yung]

--- Daniel Bump <address@hidden> wrote:
> 
> > i did a search in the sgf directory for some of the identifiers,
> but
> > grep came up empty handed [aside from sft_utils.c] .
> > 
> > any suggestions are appreciated.
> 
> The declarations of SGFCR are supposed to be in sgf_properties.h.
> This is included in the distribution but is also a Makefile
> target, automatically built from sgf_properties.def which
> is part of the sgf specifiation.
> 
> Is this file sgf_properties.h present?

it is, but it is 0 bytes.  i removed it and ran make again, which
generated the following output.

make  all-recursive
make[1]: Entering directory `/home/brian/yopy/gnugo-2.6'
Making all in utils
make[2]: Entering directory `/home/brian/yopy/gnugo-2.6/utils'
make[2]: Nothing to be done for `all'.
make[2]: Leaving directory `/home/brian/yopy/gnugo-2.6/utils'
Making all in sgf
make[2]: Entering directory `/home/brian/yopy/gnugo-2.6/sgf'
cat ./sgf_properties.def ./sgf_extras.def |\
        ./sgfgen > sgf_properties.h
/bin/sh: ./sgfgen: cannot execute binary file
make[2]: *** [sgf_properties.h] Error 126
make[2]: Leaving directory `/home/brian/yopy/gnugo-2.6/sgf'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/brian/yopy/gnugo-2.6'
make: *** [all-recursive-am] Error 2


> The sgf stuff isn't really necessary to generate a move and
> one approach would be to cut it out. This would require
> a lot of revisions but they'd be reasonably routine.

if i can get it to compile without hacks, that is preferred.


> Another thing you might want to do is to configure with
> a smaller cache size. 8Mb will probably do.




=====
.
                  {: }

   ..     the mux space conglomerate     ..
      " family values were never this good "

               www . mux space . com

__________________________________________________
Do You Yahoo!?
Send FREE Valentine eCards with Yahoo! Greetings!
http://greetings.yahoo.com