zsh-users
 help / color / mirror / code / Atom feed
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: yodl [Re: Compilation problem on Cygwin]
Date: Thu, 29 Mar 2001 12:37:51 +0400 (MSD)	[thread overview]
Message-ID: <Pine.SV4.4.33.0103291232210.26074-100000@itsrm2.mow.siemens.ru> (raw)
In-Reply-To: <20010329112755.O3478@niksula.cs.hut.fi>

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


  reply	other threads:[~2001-03-29  8:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-28  9:45 Compilation problem on Cygwin Ville Herva
2001-03-28 11:12 ` Andrej Borsenkow
2001-03-28 12:03   ` Ville Herva
2001-03-29  7:39     ` Andrej Borsenkow
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 [this message]
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.0103291232210.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).