Re: [Chicken-users] CMake cygwin can't do -0

[John Cowan]

Brandon J. Van Every scripsit:

> I can't account for build behavior with plain cmake, sans ccmake.  

Okay, I'm building with ccmake from now on.

> But if you just run a cmake from the command line, perhaps your paths
> run the wrong cmake?

No.  My path is set up so that the Cygwin directories preceded the
Windows directories, always.  In any case, I don't have native cmake on
the system at all.

> I assume you do this from a Cygwin shell, yes?  Just sanity checking.

Yes.

> Since it works on my system, our systems are clearly different.  Are all 
> your Cygwin installations recent?  I grabbed the latest greatest 1..2 
> months ago, and I unwittingly just updated various tools while 
> downloading CMake 2.4.3.  In particular here's my GCC:
> 
> Brandon J. Van address@hidden ~
> $ gcc --version
> gcc (GCC) 3.4.4 (cygming special) (gdc 0.12, using dmd 0.125)

We have the same gcc, yes.  I update Cygwin every few days, and
specifically did so yesterday and today.

> Another possibility is my Windows 2000 SP4 + Platform SDK + environment 
> + paths has something useful in it that your system doesn't have.  What 
> Windows are you using?  I wonder if there are any Cygwin symlink bugs on 
> your system.

I'm using Windows XP SP2, no MinGW, no Platform SDK.

> I wish I knew which was more consequential, a symlink or a rename.  Both 
> could be problematic.

The fact is that when I remove your symbolic links and rename the
underlying files by hand, everything works fine.  And when I patch lines
1119 and 1122 of CMakeLists.txt to say "copy" instead of "create_symlink",
everything works fine.  (I didn't bother adding a "remove", as the extra
files are harmless.)  But when I don't do these things, "csi -R srfi-1"
doesn't work.  And that is just as true whether I run cmake or ccmake;
the process is doing the same thing in either case.

Try it my way on your system.  If it works for you and it works for me,
that sounds good to me.  Here's the post-install script I'm using:

#!/bin/sh
cd /usr/local/lib
rm libchicken.dll.a
rm libuchicken.dll.a
mv libchicken-0.dll.a libchicken.dll.a
mv libuchicken-0.dll.a libchicken.dll.a

I also recommend running the following brute force "zap-chicken" script
after "make" and before "make install", which makes very sure there is
nothing lying around from earlier Chicken builds:

#!/bin/sh
cd /usr/local/bin
rm -rf *chicken* cs[ic]*
cd /usr/local/lib
rm -rf *chicken*
cd /usr/local/include
rm -rf *chicken*
cd /usr/local/man/man1
rm -rf *chicken* cs[ic]*
cd /usr/local/share
rm -rf chicken

I'm also sending you the patch with "darcs send".

-- 
John Cowan          http://www.ccil.org/~cowan        address@hidden
To say that Bilbo's breath was taken away is no description at all.  There are
no words left to express his staggerment, since Men changed the language that
they learned of elves in the days when all the world was wonderful. --The Hobbit