From: zefram@fysh.org
To: zsh-workers@sunsite.auc.dk
Subject: PATCH: RE: No rules to make zsh.mdh
Date: Mon, 20 Dec 1999 10:17:04 GMT [thread overview]
Message-ID: <199912201017.KAA10179@mango.dublin.iona.ie> (raw)
>$(dir_top)//zsh.mdh: FORCE
> @cd $(dir_top)/ && $(MAKE) $(MAKEDEFS) zsh.mdh
>
> $(dir_top)/Src/zsh.mdh:
> false # should only happen with make -n
This is slightly broken. I can't reproduce this; I'd guess that
your Makefiles have got out of synch with the recent patches.
Do "./config.status --recheck; ./config.status; make prep" from the
top-level directory to get them all rebuilt. Actually, you might need to
do a "rm **/*.mdh*" as well, if the incorrect pathnames have propagated
to the headers too.
>Note initial blank - is it correct? Is it portable?
It's correct in that I knew it could be there (actually it's always
there, exactly one space) and considred it insignificant. However,
this patch will remove it, for neatness.
diff -cr ../zsh-/Src/mkmakemod.sh ./Src/mkmakemod.sh
*** ../zsh-/Src/mkmakemod.sh Thu Dec 16 14:26:33 1999
--- ./Src/mkmakemod.sh Mon Dec 20 10:01:58 1999
***************
*** 350,356 ****
echo
done | sed 's,^\(.*\)@%@\(.*\)@%@\(.*\)/\([^/]*\)$,\1\3\2\4,'
if test -n "$other_mdhs"; then
! echo "${other_mdhs}:"
echo " false # should only happen with make -n"
echo
fi
--- 350,356 ----
echo
done | sed 's,^\(.*\)@%@\(.*\)@%@\(.*\)/\([^/]*\)$,\1\3\2\4,'
if test -n "$other_mdhs"; then
! echo "${other_mdhs}:" | sed 's,^ ,,'
echo " false # should only happen with make -n"
echo
fi
***************
*** 360,366 ****
echo
done | sed 's,^\(.*\)@%@\(.*\)@%@\(.*\)/\([^/]*\)$,\1\3\2\4,'
if test -n "$other_exports"; then
! echo "${other_exports}:"
echo " false # should only happen with make -n"
echo
fi
--- 360,366 ----
echo
done | sed 's,^\(.*\)@%@\(.*\)@%@\(.*\)/\([^/]*\)$,\1\3\2\4,'
if test -n "$other_exports"; then
! echo "${other_exports}:" | sed 's,^ ,,'
echo " false # should only happen with make -n"
echo
fi
END
reply other threads:[~1999-12-20 10:16 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=199912201017.KAA10179@mango.dublin.iona.ie \
--to=zefram@fysh.org \
--cc=zsh-workers@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).