Missing configure script?

[Could_Be_Anyone]

Ok, maybe I'm having a brain fart here..
As I understand it, the build / install procedure is now:
./configure, make, make install.

I've downloaded the CVS ( $ cvs co -r pre_5_0_beta showeq )

cd into showeq/

run ./configure

There's no such file... ????

[sea4th]

I think I understand the problem but I don't know the answer ... yet.

In 2004 the devs switched from CVS to tarballs for supporting release versions - see

http://www.showeq.net/forums/showthread.php?t=5135&highlight=5.0.0.16

But the patch is working against the CVS version - so the answer has to be what CVS token version does one use. Based on browsing the CVS I will guess from this link it is v5_0_0_16 but it is a guess. What I would really like is someones script --> the line

-d:pserver:[email protected]:cvsroo t/seq ????? co showeq5

http://cvs.sourceforge.net/viewcvs.py/seq/showeq/.cvsignore?hideattic=0&only_with_tag=v5_0_0_16

For the past couple of years I have been manually applying the patch information to get an understanding of what was being changed and using the "released" 4.x version on a RH7.2 box. I also setup FC2 with the 5.0.0.15 tarball and replacing the files from the patch tar/zip did not give a useable result on either box.

Will keep plugging away but I haven't found the bridge to cross over to the op-code search side yet. Will keep searching for info as well so this may get edited...

[kmkm]

You need to generate the configure script yourself from the checked out CVS copy: "make -f Makefile.dist all"

HTH

[bonkersbobcat]

You need to generate the configure script yourself from the checked out CVS copy: "make -f Makefile.dist all"

HTH

If this fails, you may have a version of automake that is newer then is supported by the current CVS source tree. If this is the case, look at the patch I posted in the Dev secion.

BB