zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>,
	"ZSH workers mailing list" <zsh-workers@sunsite.auc.dk>
Subject: PATCH: Re: rlimits.c recompiled on every make
Date: Fri, 7 Jul 2000 16:38:39 +0000	[thread overview]
Message-ID: <1000707163839.ZM1350@candle.brasslantern.com> (raw)
In-Reply-To: <000301bfe7ec$755bc5b0$21c9ca95@mow.siemens.ru>

On Jul 7, 12:22pm, Andrej Borsenkow wrote:
} Subject: RE: rlimits.c recompiled on every make
}
} > Here's the problem.  @RLIMITS_INC_H@ is being replaced by /dev/null; I
} > suspect the mod time of /dev/null changes whenever it's written-to, so
} > it's almost always newer than rlimits.h -- hence rlimits.h is remade,
} > and so rlimits.o is also remade.
} >
} > Please re-run configure and let me know whether you see the message
} >
} >     RLIMIT MACROS NOT FOUND:  please report to developers
} 
} No, I do no get this message. It is output only if getrlimit() is found
} but RLIMIT_* macros are missing. On Cygwin there is no getrlimit() at
} all and no message.

That is as I suspected.  OK, then, the patch below should handle it.
 
} In this case it is pretty useless to build rlimit module?

All of the rlimit commands get replaced with the `bin_notavail' stub, so
that you get a more informative error message than "command not found."

Index: configure.in
===================================================================
@@ -963,6 +963,9 @@
   AC_MSG_WARN(RLIMIT MACROS NOT FOUND:  please report to developers)
 fi])
 RLIMITS_INC_H=$zsh_cv_path_rlimit_h
+if test "$RLIMITS_INC_H" = "/dev/null"; then
+  RLIMITS_INC_H=''
+fi
 dnl rlimits.h only appears in dependencies if we are actually using it.
 dnl We are using it any time we have getrlimit, though if the macros were
 dnl not found we simply awk through /dev/null and fail to find them.
Index: Src/Builtins/rlimits.mdd
===================================================================
@@ -9,7 +9,7 @@
 
 # this file will not be made if limits are unavailable
 rlimits.h: rlimits.awk @RLIMITS_INC_H@
-	$(AWK) -f $(sdir)/rlimits.awk @RLIMITS_INC_H@ > rlimits.h
+	$(AWK) -f $(sdir)/rlimits.awk @RLIMITS_INC_H@ /dev/null > rlimits.h
 	@if grep ZLIMTYPE_UNKNOWN rlimits.h >/dev/null; then \
 	    echo >&2 WARNING: unknown limits: mail rlimits.h to developers; \
 	else :; fi

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


      reply	other threads:[~2000-07-08  8:43 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
2000-07-07  4:09     ` Bart Schaefer
2000-07-07  8:22       ` Andrej Borsenkow
2000-07-07 16:38         ` Bart Schaefer [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=1000707163839.ZM1350@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=Andrej.Borsenkow@mow.siemens.ru \
    --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).