From: "Jan Djärv" <jan.h.d@swipnet.se>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Ivan Kanis <ivan.kanis@googlemail.com>, 9372@debbugs.gnu.org
Subject: bug#9372: 24.0.50; missing header biditype.h
Date: Fri, 26 Aug 2011 07:39:59 +0200 [thread overview]
Message-ID: <4E5731AF.6020501@swipnet.se> (raw)
In-Reply-To: <jwvbovcg6ha.fsf-monnier+emacs@gnu.org>
Stefan Monnier skrev 2011-08-26 06:11:
>> timestamp newer than deps/bidi.d, the latter would be regenerated before
>> anything else happened. But maybe it doesn't work like that?
>
> No, it's the opposite: the bidi.d file from previous compilation
> (i.e. older) is used to guess whether bidi.c needs to be recompiled.
>
> Basically, the problem is that the bidi.d file should contain
> dependencies which say "if foo.c is newer than bidi.c, then recompile,
> but if foo.c doesn't exist any more, then just ignore this rule rather
> than foolishly trying to build foo.c".
> I don't know if GNU make provides such a kind of dependency (tho you
> can get it via ifeq trickery).
>
The problem is that make includes bidi.d. So the rule would have to be
if bidi.d is older than bidi.c, don't include it. I don't know if that is
possible. Also, if foo.c don't exist anymore may be an error, for example
removed from the repository by mistake.
Jan D.
next prev parent reply other threads:[~2011-08-26 5:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-25 17:00 bug#9372: 24.0.50; missing header biditype.h Ivan Kanis
2011-08-25 17:16 ` Glenn Morris
2011-08-25 17:22 ` Eli Zaretskii
[not found] ` <87pqjtxqvm.fsf@kanis.fr>
2011-08-25 19:04 ` Glenn Morris
2011-08-25 20:46 ` Jan Djärv
2011-08-25 21:47 ` Glenn Morris
2011-08-26 4:11 ` Stefan Monnier
2011-08-26 5:39 ` Jan Djärv [this message]
2011-08-26 6:34 ` Andreas Schwab
2011-08-26 7:15 ` Jan Djärv
2011-08-26 5:37 ` Jan Djärv
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=4E5731AF.6020501@swipnet.se \
--to=jan.h.d@swipnet.se \
--cc=9372@debbugs.gnu.org \
--cc=ivan.kanis@googlemail.com \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.