gnugo-devel
[Top][All Lists]
Advanced

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

Re: [gnugo-devel] gnu go for ArmLinux


From: Arend Bayer
Subject: Re: [gnugo-devel] gnu go for ArmLinux
Date: Fri, 8 Feb 2002 12:43:47 +0100 (CET)

> > 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
> 
Are you cross-compiling? This will not work directly, as during the
make process, a couple of programs have to be run on the same machine as
the compiler.

I don't know the sources of 2.6 (I assume they will be similar), but with
GNU Go 3.0.0 or 3.1.x the following should work (it is a little messy but
the easiest I can think of):
1. configure and compile GNU Go for the machine with which you are
   compiling
2. Now configure again, setting the compiler to the cross-compiler
3. remove all object files (rm engine/*.o patterns/*.o interface/*.o
   sgf/*.o engine/*.o utils/*.o) and interface/gnugo
4. Edit the file patterns/Makefile by removing all files *.db and
   *.sgf wherever they are mentioned
5. Similarly edit sgf/Makefile by removing sgf_properties.def and
   sgf_extras.def wherever they are mentioned
6. Now try to run make again.

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

I am not sure whether the above method qualifies as without hacks...
Anyone have a shorter method?

Arend





reply via email to

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