From: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>
To: Ville Herva <vherva@mail.niksula.cs.hut.fi>
Cc: Andrej Borsenkow <Andrej.Borsenkow@mow.siemens.ru>,
<zsh-users@sunsite.auc.dk>
Subject: Re: Compilation problem on Cygwin
Date: Thu, 29 Mar 2001 11:39:33 +0400 (MSD) [thread overview]
Message-ID: <Pine.SV4.4.33.0103291108240.26074-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <20010328150338.I3478@niksula.cs.hut.fi>
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
-------------------------------------------------------------------------
next prev parent reply other threads:[~2001-03-29 7:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-28 9:45 Ville Herva
2001-03-28 11:12 ` Andrej Borsenkow
2001-03-28 12:03 ` Ville Herva
2001-03-29 7:39 ` Andrej Borsenkow [this message]
2001-03-29 8:04 ` Ville Herva
2001-03-29 8:27 ` yodl [Re: Compilation problem on Cygwin] Ville Herva
2001-03-29 8:37 ` Andrej Borsenkow
2001-03-29 9:25 ` Ville Herva
2001-03-29 9:49 ` Andrej Borsenkow
2001-03-29 10:09 ` Ville Herva
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.SV4.4.33.0103291108240.26074-100000@itsrm2.mow.siemens.ru \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=vherva@mail.niksula.cs.hut.fi \
--cc=zsh-users@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).