All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: jongman.heo@samsung.com, Thomas Rast <trast@student.ethz.ch>,
	git <git@vger.kernel.org>, Antoine Pelisse <apelisse@gmail.com>
Subject: Re: Segmentation fault with latest git (070c57df)
Date: Fri, 1 Feb 2013 02:06:22 -0500	[thread overview]
Message-ID: <20130201070622.GA700@sigill.intra.peff.net> (raw)
In-Reply-To: <20130201063638.GD29973@sigill.intra.peff.net>

On Fri, Feb 01, 2013 at 01:36:38AM -0500, Jeff King wrote:

> It seems like building each object file should depend on its dependency
> file (but only when COMPUTE_HEADER_DEPENDENCIES is on, of course), since
> otherwise we cannot know if we have the right dependencies or not.
> 
> Something like this almost works, I think:
> [...]
> +$(C_OBJ): %.o: %.c GIT-CFLAGS $(missing_dep_dirs) $(call dep_file, %.o)

Actually that would not work, as we do not have a rule to create
.depend/foo.o.d. We can add one, but it gets pretty hairy (and
replicates much of the normal build rule). A much simpler way is to just
find the missing dep files and force compilation of their matching
objects. Like:

diff --git a/Makefile b/Makefile
index 6b42f66..f94e8b9 100644
--- a/Makefile
+++ b/Makefile
@@ -1843,8 +1843,14 @@ dep_args = -MF $(dep_file) -MMD -MP
 	@mkdir -p $@
 
 missing_dep_dirs := $(filter-out $(wildcard $(dep_dirs)),$(dep_dirs))
+missing_dep_files := $(filter-out $(wildcard $(dep_files)),$(dep_files))
+# we want to rewrite "foo/.depend/bar.o.d" into "foo/bar.o", but
+# make's patsubst is not powerful enough to remove something from the middle of
+# a string. Hack around it by shelling out.
+obj_files_with_missing_deps := $(shell echo $(missing_dep_files:.d=) | tr ' ' '\n' | sed 's,.depend/,,')
 dep_file = $(dir $@).depend/$(notdir $@).d
 dep_args = -MF $(dep_file) -MMD -MP
+$(obj_files_with_missing_deps): FORCE
 ifdef CHECK_HEADER_DEPENDENCIES
 $(error cannot compute header dependencies outside a normal build. \
 Please unset CHECK_HEADER_DEPENDENCIES and try again)

which does solve the problem, but that shell hack is nasty. It would be
much simpler if we stored the dependency for foo/bar.o as
".depend/foo/bar.o.d", rather than "foo/.depend/bar.o.d", as then we
would patsubst it away. Or maybe there is some clever way to convince
make to do what I want here. Suggestions welcome.

-Peff

  reply	other threads:[~2013-02-01  7:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-01  1:31 Re: Segmentation fault with latest git (070c57df) 허종만
2013-02-01  1:40 ` Junio C Hamano
2013-02-01  6:36   ` Jeff King
2013-02-01  7:06     ` Jeff King [this message]
2013-02-01  7:09     ` Jeff King
  -- strict thread matches above, loose matches on Subject: below --
2013-02-04  2:18 Re: Re: Re: " Jongman Heo
2013-02-04  3:40 ` Jonathan Nieder
2013-01-31  7:27 Jongman Heo
2013-01-31  7:55 ` Jeff King
2013-01-31  8:42   ` Thomas Rast
2013-01-31  8:54     ` Jeff King
2013-01-31  1:35 Jongman Heo
2013-01-31  6:49 ` Jeff King
2013-01-31  7:02   ` Antoine Pelisse
2013-01-31  7:35     ` Jeff King
2013-02-04  6:58 ` Jongman Heo
2013-02-04  7:13   ` Junio C Hamano
2013-02-04  8:37     ` Jeff King
2013-02-04  9:16       ` Junio C Hamano
2013-02-04  9:29         ` Junio C Hamano
2013-02-04  9:45           ` Jeff King
2013-02-04  9:38         ` Jeff King
2013-02-04 16:46           ` Junio C Hamano
2013-02-04 18:34             ` Jonathan Nieder
2013-05-15  3:14               ` sam
2013-05-15  3:22                 ` sam
2013-05-16 13:12                 ` Ramkumar Ramachandra
2013-05-16 13:21                   ` Ramkumar Ramachandra

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=20130201070622.GA700@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=apelisse@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jongman.heo@samsung.com \
    --cc=trast@student.ethz.ch \
    /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.
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.