git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jongman Heo <jongman.heo@samsung.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
	Thomas Rast <trast@student.ethz.ch>, git <git@vger.kernel.org>,
	Antoine Pelisse <apelisse@gmail.com>
Subject: Re: Re: Re: Re: Re: Segmentation fault with latest git (070c57df)
Date: Mon, 04 Feb 2013 02:18:06 +0000 (GMT)	[thread overview]
Message-ID: <19086873.858651359944284535.JavaMail.weblogic@epml01> (raw)


Jonathan Nieder wrote:

> Jongman Heo wrote:
>
>>> But it doesn't stimulate any prerequisites in make, which is weird.
>>> What's in builtin/.depend/fetch.o.d?
>[...]
>> please see below~.
>>
>> $ cat builtin/.depend/fetch.o.d            
>> fetch.o: builtin/fetch.c cache.h git-compat-util.h compat/bswap.h \
>
>That's the problem.  See the following thread:
>
>  http://thread.gmane.org/gmane.comp.version-control.git/185625/focus=185680
>
>Currently when COMPUTE_HEADER_DEPENDENCIES=auto git tests for
>dependency generation support by checking the output and exit status
>from the following command:
>
>$(CC) $(ALL_CFLAGS) -c -MF /dev/null -MMD -MP \
>-x c /dev/null -o /dev/null 2>&1
>
>Perhaps this can be improved?  Even something as simple as a ccache
>version test could presumably help a lot.
>
>Hope that helps,
>Jonathan

Hi,

Unfortunately, the patch didn't help to me.
Anyway, ccache is the culprit (I'm using ccache 2.4 version).

If I disable ccache using CCACHE_DISABLE=1, then the issue doesn't happen. Thanks.

Best regards,
Jongman Heo.

             reply	other threads:[~2013-02-04  2:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-04  2:18 Jongman Heo [this message]
2013-02-04  3:40 ` Segmentation fault with latest git (070c57df) Jonathan Nieder

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=19086873.858651359944284535.JavaMail.weblogic@epml01 \
    --to=jongman.heo@samsung.com \
    --cc=apelisse@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jrnieder@gmail.com \
    --cc=peff@peff.net \
    --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 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).