RE: [Gcl-devel] GCL on mingw - patches

[Mike Thomas]

Hi Vadim.

One last bit of information to help you with MSYS automake etc.

Following up on your problems and on Jim's advice below, on the weekend I
did a clean MSYS/MinGW install (using the latest versions of everything) on
my home machine (Win 2000 Pro) to make sure that recent MSYS changes have
not broken automake.

It all went perfectly except that I strongly advise you not to use MSYS
1.0.10 Release Candidate 3, which has the annoying bug of launching a DOS
shell window whenever it launches a subprocess.  I used RC2 instead and
everything was fine.  The RC3 problem is apparently reported and a fix will
be in RC4.

Cheers

Mike Thomas.



| On Tue, 2003-12-30 at 12:16, Vadim V. Zhytnikov wrote:
|
| > AFAIK we don't need automake for GCL, just
| > autoconf if we want to recreate configure
| > from configure.in.  But automake is required
| > to build CVS Maxima.
| >
| > Originally I installed mingw and MSYS only
| > (in was not aware that msysDTK stands for
| > msys Developper Tool Kit).  Later installing
| > msysDTK I was pleased to find collection
| > of useful tools like perl, ... and
| > autoconf/automake scripts in /bin directory.
| > By any attempt to run autoconf in GCL dir
| > complained about missing Autom4te/General.pm
| > perl module.
|
| Vadim,
|
| I don't pretend to understand mingw/msys, but I think your installation
| is somehow damaged. I believe I have the same packages installed you
| have, but I have a working automake and autoconf. I see this:
|
| % find . -name General.pm
| ./msys/1.0/share/autoconf/Autom4te/General.pm
| ./msys/1.0/share/automake-1.7/Automake/General.pm
| %
|
| You might just want to re-install.
|
| --Jim