From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "Bart Schaefer" <schaefer@candle.brasslantern.com>,
"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: RE: rlimits.c recompiled on every make
Date: Thu, 6 Jul 2000 10:35:24 +0400 [thread overview]
Message-ID: <000001bfe714$5d941050$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <1000705042718.ZM21479@candle.brasslantern.com>
>
> On Jul 4, 9:44pm, Andrej Borsenkow wrote:
> } Subject: rlimits.c recompiled on every make
> }
> } at least on Cygwin with static zsh. Even if everything is
> up to date.
>
> Is the problem with Aliases/rlimits.c or Builtins/rlimits.c ?
>
To my understanding of GNU make, Builtins/rlimit.c
bash-2.04$ make
make[1]: Entering directory `/usr/build/zsh/Src'
make[2]: Entering directory `/usr/build/zsh/Src'
make[3]: Entering directory `/usr/build/zsh/Src/Aliases'
make[3]: Leaving directory `/usr/build/zsh/Src/Aliases'
make[3]: Entering directory `/usr/build/zsh/Src/Builtins'
make[3]: Leaving directory `/usr/build/zsh/Src/Builtins'
make[3]: Entering directory `/usr/build/zsh/Src/Modules'
make[4]: Entering directory `/usr/build/zsh/Src/Zle'
make[4]: Leaving directory `/usr/build/zsh/Src/Zle'
make[3]: Leaving directory `/usr/build/zsh/Src/Modules'
make[3]: Entering directory `/usr/build/zsh/Src/Zle'
make[3]: Leaving directory `/usr/build/zsh/Src/Zle'
make[2]: Leaving directory `/usr/build/zsh/Src'
rm -f stamp-modobjs.tmp
make[2]: Entering directory `/usr/build/zsh/Src'
`zshpaths.h' is up to date.
echo '' builtin.o compat.o cond.o exec.o glob.o hashtable.o hist.o
init.o input.
o jobs.o lex.o linklist.o loop.o math.o mem.o module.o options.o
params.o parse.
o pattern.o prompt.o signals.o signames.o subst.o text.o utils.o watch.o
>> ../S
rc/stamp-modobjs.tmp
make[3]: Entering directory `/usr/build/zsh/Src/Aliases'
make[3]: Leaving directory `/usr/build/zsh/Src/Aliases'
make[3]: Entering directory `/usr/build/zsh/Src/Builtins'
gawk -f /usr/src/zsh/Src/Builtins/rlimits.awk /dev/null > rlimits.h
gcc -c -I. -DHAVE_CONFIG_H -Wall -Wno-implicit -Wmissing-prototypes -gg
db -o r
limits.o /usr/src/zsh/Src/Builtins/rlimits.c
rlimits.pro:2: warning: `showlimits' declared `static' but never defined
rlimits.pro:3: warning: `printulimit' declared `static' but never
defined
rlimits.pro:4: warning: `bin_limit' declared `static' but never defined
rlimits.pro:5: warning: `bin_unlimit' declared `static' but never
defined
rlimits.pro:6: warning: `bin_ulimit' declared `static' but never defined
echo '' rlimits.o | sed 's" " Builtins/"g' >>
../../Src/stamp-modobjs.tmp
echo '' sched.o | sed 's" " Builtins/"g' >> ../../Src/stamp-modobjs.tmp
make[3]: Leaving directory `/usr/build/zsh/Src/Builtins'
.....
-andrej
next prev parent reply other threads:[~2000-07-06 6:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-04 17:44 Andrej Borsenkow
2000-07-05 4:27 ` Bart Schaefer
2000-07-06 6:35 ` Andrej Borsenkow [this message]
2000-07-07 4:09 ` Bart Schaefer
2000-07-07 8:22 ` Andrej Borsenkow
2000-07-07 16:38 ` PATCH: " Bart Schaefer
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='000001bfe714$5d941050$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--cc=schaefer@candle.brasslantern.com \
--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).