how to maje xboard 4.4.2?

[Volker Pittlik]

There is no configure script in xboard-4.4.2.tar.gz. Copying it from 4.4.1 and trying to use it doesn't.

vp

[Josh Pettus]

You can run "./autogen.sh" first if it's there.

[Volker Pittlik]

You can run "./autogen.sh" first if it's there.

Thanks. Had to get the "flex" package additionally but seems to work so far.

vp

[H.G.Muller]

Is this still not solved? I should cmplain to Arun then. When he makes the release tar ball, a generated 'configure' file is supposed to be packed with it. There should also go a parser.c into the tar ball, so people would not need flex. In fact there is one in the tar ball, but it is in the winboard directory. (People that compile WinBoard with MSVC in general do not have access to flex.)

For 4.4.3 I made the WinBoard compile use an included parser.c in the xboard folder, so that the XBoard compile automatically uses it too.

[Volker Pittlik]

Is this still not solved? I should cmplain to Arun then. When he makes the release tar ball, a generated 'configure' file is supposed to be packed with it. There should also go a parser.c into the tar ball,...

In xboard-4.4.3.20100220.tar.gz (and I believe in 4.4.2 too) 'configure' and 'parser.c' are missing. However using autogen.sh is a matter of seconds and getting flex is also only a one-liner. Maybe a short hint in the README would prevent further troble.

vp

[H.G.Muller]

Ah, OK. It is from a development release, not the 'official' 4.4.2 release. I guess the procedure I described is only followed for tar balls that can be downloaded from http://ftp.gnu.org/gnu/xboard/ . Tar balls loaded directly from the git repository are just reflecting the exact state of the repository, which does not contain any generated files. For this reason I pushed to make an exception for parser.c, and keep it in git even if though it is a generated file, not a source file.

./autogen.sh is also problematic, becase it requires all kind of packages that people have normally not installed (but you apparently have). Like autotools, automake, autoconf. I am not een sure exactly what is needed; for me it now also runs, and the only memory that lingers is that it was hard to get it running... So perhaps we should try to keep a version of the generated ./configure s well, so that the git tar balls are more like the distribution tar balls.