From: Ray Andrews <rayandrews@eastlink.ca>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: can't make
Date: Tue, 18 Nov 2014 16:34:31 -0800 [thread overview]
Message-ID: <546BE597.8040503@eastlink.ca> (raw)
All,
I was making away, trying a few things, then I tried this:
$ ./configure --enable-zsh-debug
And the result was this:
$ make -s
cd .. && /bin/sh $top_srcdir/Src/mkmakemod.sh Src Makemod
creating Src/Makemod.in
config.status: creating Src/Makemod
/bin/sh: 2: cd: can't cd to zsh.mdd
Makemod:374: recipe for target 'headers' failed
make[2]: *** [headers] Error 1
Makefile:452: recipe for target 'headers' failed
make[1]: *** [headers] Error 2
Makefile:190: recipe for target 'all' failed
make: *** [all] Error 1
... I configured plain vanilla again, but still get 'make' errors.
FWIW 'zsh.mdd' was there, but it's a file, not a directory. I
deleted it and tried again. This time:
config.status: executing config.modules commands
creating ./config.modules
./config.status: 41: ./config.modules.sh: Syntax error: end of file
unexpected (expecting ")")
Makefile:378: recipe for target 'config.modules' failed
make: *** [config.modules] Error 2
... I noticed that 'config.modules.sh' was much shorter than before, so
I copied in an untouched version. Reran './configure' and 'make -s'
but the error was the same.
I tried again in a virgin copy and './configure --enable-zsh-debug' worked
fine, so whatever was wrong above must have been something I did and
it's probably not worth worrying about, but if anyone does have an insight
into what went wrong, and why I can't restore it, I'd be grateful.
Particularly that 'zsh.mdd' being a file, not a directory, seems very
strange.
next reply other threads:[~2014-11-19 1:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 0:34 Ray Andrews [this message]
2014-11-19 2:56 ` Bart Schaefer
2014-11-19 5:07 ` Ray Andrews
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=546BE597.8040503@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.org \
/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).