From: Zefram <zefram@fysh.org>
To: Oliver Kiddle <opk@u.genie.co.uk>
Cc: Zsh workers <zsh-workers@sunsite.auc.dk>
Subject: Re: Empty .pro files causing compiler warnings
Date: Tue, 2 May 2000 14:41:54 +0100 (BST) [thread overview]
Message-ID: <E12mcvy-00020z-00@crucigera.fysh.org> (raw)
In-Reply-To: <390EC13F.851CD8A9@u.genie.co.uk> from Oliver Kiddle at "May 2, 2000 12:51:27 pm"
Oliver Kiddle wrote:
> The patch below fixes this on AIX
>by putting a comment in all .pro files but note no 'PATCH' in the
>subject. This is because GNU make doesn't seem to cope with the
>multi-line sed. Can someone who knows how to do multi-line commands in
>a Makefile please fix this up properly.
diff -c -u -r1.1.1.13 Makemod.in.in
--- Src/Makemod.in.in 2000/01/05 01:41:27 1.1.1.13
+++ Src/Makemod.in.in 2000/05/02 13:38:05
@@ -82,8 +82,10 @@
$(AWK) -f $(sdir_src)/makepro.awk $< $(subdir) > $@
.syms.epro:
- sed -n '/^E/{s/^E//;p;}' < $< > $@
- sed -n '/^L/{s/^L//;p;}' < $< > `echo $@ | sed 's/\.epro$$/.pro/'`
+ (echo '/* Generated automatically */'; sed -n '/^E/{s/^E//;p;}' < $<) \
+ > $@
+ (echo '/* Generated automatically */'; sed -n '/^L/{s/^L//;p;}' < $<) \
+ > `echo $@ | sed 's/\.epro$$/.pro/'`
PROTODEPS = $(sdir_src)/makepro.awk
diff -c -u -r1.179 ChangeLog
--- ChangeLog 2000/05/02 13:08:19 1.179
+++ ChangeLog 2000/05/02 13:39:09
@@ -1,3 +1,8 @@
+2000-05-02 Andrew Main <zefram@zsh.org>
+
+ * zefram103: Src/Makemod.in.in: make sure .{e,}pro files are
+ non-empty, to keep the AIX compiler quiet.
+
2000-05-02 Peter Stephenson <pws@cambridgesiliconradio.com>
* 11066: Src/exec.c: suppress doing in and/or when at the end
-zefram
prev parent reply other threads:[~2000-05-02 13:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 11:51 Oliver Kiddle
2000-05-02 13:41 ` Zefram [this message]
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=E12mcvy-00020z-00@crucigera.fysh.org \
--to=zefram@fysh.org \
--cc=opk@u.genie.co.uk \
--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).