Compilation problem on Cygwin

Compilation problem on Cygwin

[Ville Herva]

With the latest CVS and 4.0.1pre2:

> uname -a 
CYGWIN_NT-4.0 ENIGMA 1.1.8(0.34/3/2) 2001-01-31 10:08 i686 unknown
> cvs -d:pserver:anonymous@cvs.zsh.sourceforge.net:/cvsroot/zsh login
> export CVSROOT=:pserver:anonymous@cvs.zsh.sourceforge.net:/cvsroot/zsh
> cvs -z3 co zsh                               
> cd zsh
> ./Util/preconfig           
> ./configure --prefix=/usr            
> make
make[1]: Entering directory /home/vherva/zsh/zsh/Src'
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
./config.status: not found
make[2]: Entering directory /home/vherva/zsh/zsh/Src'
make[2]: Makemod: No such file or directory
make[2]: *** No rule to make target \rakemod'.  Stop.
make[2]: Leaving directory /home/vherva/zsh/zsh/Src'
make[2]: Entering directory /home/vherva/zsh/zsh/Src'
make[2]: Makemod: No such file or directory
make[2]: *** No rule to make target \rakemod'.  Stop.
make[2]: Leaving directory /home/vherva/zsh/zsh/Src'
make[1]: *** [headers] Error 2
make[1]: Leaving directory /home/vherva/zsh/zsh/Src'
make: *** [all] Error 1

Any ideas? Configure is happy.


Also, it seems that the Linux configure does not detect the lack of yodl,
but the make fails with an error message that is not that elucidating:

case zsh.1 in \
  */*) target=zsh.1 ;; \
  *) target=./zsh.1 ;; \
esac; \
case ': yodl' in :*) ;; *) \
    : yodl -I. -w zman.yo version.yo zsh.yo | sed -e '1s/\\-/-/g' -e
'/^\.'\''/d
' > $target \
;; esac; \
test -f $target
make[1]: *** [zsh.1] Error 1
make[1]: Leaving directory /mnt/ext2-2/vherva/zsh/zsh/Doc'
make: *** [all] Error 1

 
-- v --

v@iki.fi

Re: Compilation problem on Cygwin

[Andrej Borsenkow]

I think I have seen this once ... can you please try separate build
directory? I probably never tried it in src dir.

Another possibilities are:

- binary/text mount. Zsh is not very happy with DOS lineendings. Please,
check how your home is mounted; if it is text, remount it in binary (you
porbably need to repeat cvs checkout to get correct lineendings)

- you are on FAT and Cygwin does not understand that config.status is
executable. Do we have #!/bin/sh there? (I presume, yes).

- every now and then there are bug reports for CVS under Cygwin.

I'll be able to do more next week.

-andrej

On Wed, 28 Mar 2001, Ville Herva wrote:

> With the latest CVS and 4.0.1pre2:
>
> > uname -a
> CYGWIN_NT-4.0 ENIGMA 1.1.8(0.34/3/2) 2001-01-31 10:08 i686 unknown
> > cvs -d:pserver:anonymous@cvs.zsh.sourceforge.net:/cvsroot/zsh login
> > export CVSROOT=:pserver:anonymous@cvs.zsh.sourceforge.net:/cvsroot/zsh
> > cvs -z3 co zsh
> > cd zsh
> > ./Util/preconfig
> > ./configure --prefix=/usr
> > make
> make[1]: Entering directory /home/vherva/zsh/zsh/Src'
> cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
> creating Src/Makemod.in
> ./config.status: not found
> make[2]: Entering directory /home/vherva/zsh/zsh/Src'
> make[2]: Makemod: No such file or directory
> make[2]: *** No rule to make target
> akemod'.  Stop.
> make[2]: Leaving directory /home/vherva/zsh/zsh/Src'
> make[2]: Entering directory /home/vherva/zsh/zsh/Src'
> make[2]: Makemod: No such file or directory
> make[2]: *** No rule to make target
> akemod'.  Stop.
> make[2]: Leaving directory /home/vherva/zsh/zsh/Src'
> make[1]: *** [headers] Error 2
> make[1]: Leaving directory /home/vherva/zsh/zsh/Src'
> make: *** [all] Error 1
>
> Any ideas? Configure is happy.
>
>
> Also, it seems that the Linux configure does not detect the lack of yodl,
> but the make fails with an error message that is not that elucidating:
>
> case zsh.1 in \
>   */*) target=zsh.1 ;; \
>   *) target=./zsh.1 ;; \
> esac; \
> case ': yodl' in :*) ;; *) \
>     : yodl -I. -w zman.yo version.yo zsh.yo | sed -e '1s/\\-/-/g' -e
> '/^\.'\''/d
> ' > $target \
> ;; esac; \
> test -f $target
> make[1]: *** [zsh.1] Error 1
> make[1]: Leaving directory /mnt/ext2-2/vherva/zsh/zsh/Doc'
> make: *** [all] Error 1
>
>
> -- v --
>
> v@iki.fi
>
>

Re: Compilation problem on Cygwin

[Ville Herva]

On Wed, Mar 28, 2001 at 03:12:31PM +0400, you [Andrej Borsenkow] claimed:
> I think I have seen this once ... can you please try separate build
> directory? I probably never tried it in src dir.

I did 
cd ..
mkdir build
cd build
../configure --prefix=/usr
make

and it gave

make[1]: Entering directory /home/vherva/zsh/build/Src'
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
./config.status: not found
make[2]: Entering directory /home/vherva/zsh/build/Src'
make[2]: Makemod: No such file or directory
make[2]: *** No rule to make target \rakemod'.  Stop.
make[2]: Leaving directory /home/vherva/zsh/build/Src'
make[2]: Entering directory /home/vherva/zsh/build/Src'
make[2]: Makemod: No such file or directory
make[2]: *** No rule to make target \rakemod'.  Stop.
make[2]: Leaving directory /home/vherva/zsh/build/Src'
make[1]: *** [headers] Error 2
make[1]: Leaving directory /home/vherva/zsh/build/Src'
make: *** [all] Error 1

 
> Another possibilities are:
> 
> - binary/text mount. Zsh is not very happy with DOS lineendings. Please,
> check how your home is mounted; if it is text, remount it in binary (you
> porbably need to repeat cvs checkout to get correct lineendings)

I checked mount. It should be binary:
c:\home             /home               user         binmode
 
> - you are on FAT and Cygwin does not understand that config.status is
> executable. Do we have #!/bin/sh there? (I presume, yes).

This is NTFS. I do have /bin/sh.

> - every now and then there are bug reports for CVS under Cygwin.

This happened with 4.0.1pre2 as well.
 
> I'll be able to do more next week.

Thanks!


-- v --

v@iki.fi

Re: Compilation problem on Cygwin

[Andrej Borsenkow]

One more possibility (and I'm pretty sure it is it): the temporary files
are created on text-mounted file system and then simply copied into /home
and get DOS lineend.

anybody knows where configure creates temporary files?

Ville, could you check

- config.status, and probably a couple of makefiles (Src/Makemod,
Src/Makefile) for CR-LF? Better copy over to Unix (to avoid Cygwin
sideeffects; do not forget bin mode :-). If you see something like
"#!/bin/shCR" - it canot work of course.

- how your /tmp (and may be TMP, TEMP, TMPDIR) are mounted? If they are
inside text-mounted filesystem? Note, that Cygwin defaulted to text mount;
since 1.1.8 (I believe) it defaults to binary, but it won't change
defaults by update.

-andrej


 On Wed, 28 Mar 2001, Ville Herva wrote:

> On Wed, Mar 28, 2001 at 03:12:31PM +0400, you [Andrej Borsenkow] claimed:
> > I think I have seen this once ... can you please try separate build
> > directory? I probably never tried it in src dir.
>
> I did
> cd ..
> mkdir build
> cd build
> ../configure --prefix=/usr
> make
>
> and it gave
>
> make[1]: Entering directory /home/vherva/zsh/build/Src'
> cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
> creating Src/Makemod.in
> ./config.status: not found
> make[2]: Entering directory /home/vherva/zsh/build/Src'
> make[2]: Makemod: No such file or directory
> make[2]: *** No rule to make target
> akemod'.  Stop.
> make[2]: Leaving directory /home/vherva/zsh/build/Src'
> make[2]: Entering directory /home/vherva/zsh/build/Src'
> make[2]: Makemod: No such file or directory
> make[2]: *** No rule to make target
> akemod'.  Stop.
> make[2]: Leaving directory /home/vherva/zsh/build/Src'
> make[1]: *** [headers] Error 2
> make[1]: Leaving directory /home/vherva/zsh/build/Src'
> make: *** [all] Error 1
>
>
> > Another possibilities are:
> >
> > - binary/text mount. Zsh is not very happy with DOS lineendings. Please,
> > check how your home is mounted; if it is text, remount it in binary (you
> > porbably need to repeat cvs checkout to get correct lineendings)
>
> I checked mount. It should be binary:
> c:\home             /home               user         binmode
>
> > - you are on FAT and Cygwin does not understand that config.status is
> > executable. Do we have #!/bin/sh there? (I presume, yes).
>
> This is NTFS. I do have /bin/sh.
>
> > - every now and then there are bug reports for CVS under Cygwin.
>
> This happened with 4.0.1pre2 as well.
>
> > I'll be able to do more next week.
>
> Thanks!
>
>
> -- v --
>
> v@iki.fi
>
>

-- 
------------------------------------------------------------------------
Andrej Borsenkow 		Fax:   +7 (095) 737 2747
Siemens ICP ITS Moscow		Tel:   +7 (095) 737 2723

E-Mail: Andrej.Borsenkow@mow.siemens.ru
-------------------------------------------------------------------------

Re: Compilation problem on Cygwin

[Ville Herva]

On Thu, Mar 29, 2001 at 11:39:33AM +0400, you [Andrej Borsenkow] claimed:
> One more possibility (and I'm pretty sure it is it): the temporary files
> are created on text-mounted file system and then simply copied into /home
> and get DOS lineend.
> 
> anybody knows where configure creates temporary files?
> 
> Ville, could you check
> 
> - config.status, and probably a couple of makefiles (Src/Makemod,
> Src/Makefile) for CR-LF? Better copy over to Unix (to avoid Cygwin
> sideeffects; do not forget bin mode :-). If you see something like
> "#!/bin/shCR" - it canot work of course.

od -ah Src/Makefile config.status Src/Makemod.in | grep -i cr

show nothing for those files (of course I don't have Makemod, just
Makemod.in and that's what make complains about). That's on unix.

I double checked with a DOS file, and it did show the CR's.

> - how your /tmp (and may be TMP, TEMP, TMPDIR) are mounted? If they are
> inside text-mounted filesystem? Note, that Cygwin defaulted to text mount;
> since 1.1.8 (I believe) it defaults to binary, but it won't change
> defaults by update.

I have 

c:\cygwin           /                   system       binmode

and I just changed 
export TMP=/tmp
export TEMP=/tmp
(nothing mounted on /tmp, it's just a dir under /).

That didn't help.
 
> -andrej

I'll try to play with this myself a bit. I'll post if I can't find out
anything useful.



-- v --

v@iki.fi

yodl [Re: Compilation problem on Cygwin]

[Ville Herva]

On Thu, Mar 29, 2001 at 11:39:33AM +0400, you [Andrej Borsenkow] claimed:
> One more possibility (and I'm pretty sure it is it): the temporary files
> are created on text-mounted file system and then simply copied into /home
> and get DOS lineend.

mlmakemod.sh was the build step that failed. So I played a bit with.

Doing
top_srcdir=../zsh /bin/bash ../zsh/Src/mkmakemod.sh Src Makemod

instead of 
top_srcdir=../zsh /bin/sh ../zsh/Src/mkmakemod.sh Src Makemod
which is what the make tries to do, helped. It now created Makemod.in.

So I replaced /bin/sh.exe with /bin/bash.exe and started the build from
scratch (rm -rf build, configure etc).

It now works. I'm still not sure what the problem was.

Now I have the same problem as with Linux, though.

configure says

checking for yodl... no

but the compilation still fails with

case ': yodl' in :*) ;; *) \
    : yodl -I../../zsh/Doc -w zman.yo version.yo ../../zsh/Doc/zsh.yo | sed
-e '1s/\\-/-/g' -e '/^\.'\''/d' > $target \
;; esac; \
test -f $target
make[1]: *** [zsh.1] Error 1
make[1]: Leaving directory /home/vherva/zsh/build/Doc'
make: *** [all] Error 1

presumably just beacause of the lacking yodl. Is yodl necessary for the
build? If so, configure should propably barf?

On linux, 'make -j3' does not work BTW ('make' works), but I think that's
not a biggie ;).

 
-- v --

v@iki.fi

Re: yodl [Re: Compilation problem on Cygwin]

[Andrej Borsenkow]

On Thu, 29 Mar 2001, Ville Herva wrote:

> On Thu, Mar 29, 2001 at 11:39:33AM +0400, you [Andrej Borsenkow] claimed:
> > One more possibility (and I'm pretty sure it is it): the temporary files
> > are created on text-mounted file system and then simply copied into /home
> > and get DOS lineend.
>
> mlmakemod.sh was the build step that failed. So I played a bit with.
>
> Doing
> top_srcdir=../zsh /bin/bash ../zsh/Src/mkmakemod.sh Src Makemod
>
> instead of
> top_srcdir=../zsh /bin/sh ../zsh/Src/mkmakemod.sh Src Makemod
> which is what the make tries to do, helped. It now created Makemod.in.
>
> So I replaced /bin/sh.exe with /bin/bash.exe and started the build from
> scratch (rm -rf build, configure etc).
>
> It now works. I'm still not sure what the problem was.
>

Hmm ... On cygwin /bin/sh is actually ash and ash != bash. Have you the
actual ash version? Else you probably have to report this on Cygwin list.
Looks like a problem (bug?) in ash.

Still, I wonder why I do not have this problem (now). Try to update ash
first.

> Now I have the same problem as with Linux, though.
>
> configure says
>
> checking for yodl... no
>
> but the compilation still fails with
>
> case ': yodl' in :*) ;; *) \
>     : yodl -I../../zsh/Doc -w zman.yo version.yo ../../zsh/Doc/zsh.yo | sed
> -e '1s/\\-/-/g' -e '/^\.'\''/d' > $target \
> ;; esac; \
> test -f $target
> make[1]: *** [zsh.1] Error 1
> make[1]: Leaving directory /home/vherva/zsh/build/Doc'
> make: *** [all] Error 1
>
> presumably just beacause of the lacking yodl. Is yodl necessary for the
> build? If so, configure should propably barf?
>

Yodl is not needed if you build from tarball, because it includes man
pages and info files. I believe, yodl is needed if you build from CVS. The
problem is, how can configure know if it was tarball or CVS?

I build from src mounted off Unix where I do have yodl so I do not have
this problem.

-andrej

Re: yodl [Re: Compilation problem on Cygwin]

[Ville Herva]

On Thu, Mar 29, 2001 at 12:37:51PM +0400, you [Andrej Borsenkow] claimed:
> On Thu, 29 Mar 2001, Ville Herva wrote:
>
> Hmm ... On cygwin /bin/sh is actually ash and ash != bash. 

Yes.

> Have you the actual ash version? 

ash latest/ash/ash-20010129.tar.gz 34747

> Else you probably have to report this on Cygwin list. Looks like a problem
> (bug?) in ash.

Ok.
 
> Still, I wonder why I do not have this problem (now). Try to update ash
> first.
> 
> Yodl is not needed if you build from tarball, because it includes man
> pages and info files. I believe, yodl is needed if you build from CVS. The
> problem is, how can configure know if it was tarball or CVS?

Check if the man pages are already there?

> I build from src mounted off Unix where I do have yodl so I do not have
> this problem.

I'll try that.



-- v --

v@iki.fi

Re: yodl [Re: Compilation problem on Cygwin]

[Andrej Borsenkow]

On Thu, 29 Mar 2001, Ville Herva wrote:

> >
> > Yodl is not needed if you build from tarball, because it includes man
> > pages and info files. I believe, yodl is needed if you build from CVS. The
> > problem is, how can configure know if it was tarball or CVS?
>
> Check if the man pages are already there?
>

If you volunteer to make clean configure check for it ... Do not forget -
CVS is for developers. It assumes, that you have complete environment -
and in case of Zsh it includes yodl. I do not see any need to complicate
things any further. Better is to port yodl to Cygwin (if any port is
needed).

> > I build from src mounted off Unix where I do have yodl so I do not have
> > this problem.
>
> I'll try that.
>
>

I mean, I first build zsh on Unix, that creates man/info and then build on
Cygwin.

-andrej

Re: yodl [Re: Compilation problem on Cygwin]

[Ville Herva]

On Thu, Mar 29, 2001 at 01:49:51PM +0400, you [Andrej Borsenkow] claimed:
> 
> If you volunteer to make clean configure check for it ... Do not forget -
> CVS is for developers. It assumes, that you have complete environment -
> and in case of Zsh it includes yodl. I do not see any need to complicate
> things any further. Better is to port yodl to Cygwin (if any port is
> needed).

True. Perhaps it's not worth it.
 
> > > I build from src mounted off Unix where I do have yodl so I do not have
> > > this problem.
> >
> > I'll try that.
> 
> I mean, I first build zsh on Unix, that creates man/info and then build on
> Cygwin.

Yeah. I understood that. I just did that, and now I actually have a working
zsh-4.0.1pre2 (CVS current) on Cygwin. Ah, the joy of the new completition!


-- v --

v@iki.fi