unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Rainer M Krug <Rainer@krugs.de>
To: notmuch@notmuchmail.org
Subject: Re: Build broken on OS X 10.9
Date: Sat, 02 Nov 2013 17:07:10 +0100	[thread overview]
Message-ID: <m2iowa949d.fsf@krugs.de> (raw)
In-Reply-To: m2fvrepzdu.fsf@guru.guru-group.fi

Tomi Ollila <tomi.ollila@iki.fi> writes:

> On Sat, Nov 02 2013, Rainer M Krug <Rainer@krugs.de> wrote:
>
>> Tomi Ollila <tomi.ollila@iki.fi> writes:
>>
>>> On Fri, Nov 01 2013, Michael Phillips <michaelalanphillips@gmail.com> wrote:
>>>
>>>> On Fri, Nov 1, 2013 at 1:44 AM, Tomi Ollila <tomi.ollila@iki.fi> wrote:
>>>>> Hmm, it seems the rule doing that says @mkdir -p .deps/$(@D) ...
>>>>>
>>>>> does `mkdir -p xyzdir/.` fail in OS X 10.9 (Mavericks) ?
>>>>
>>>> $ mkdir -p xyzdir/.
>>>>
>>>> mkdir: xyzdir/.: No such file or directory
>>>>
>>>> Good catch! So mkdir changed between 10.8 and 10.9.
>>>
>>> Quick(&dirty?) solution would be to change the in quetsion recipes to format:
>>>
>>> @-mkdir -p .deps/$(@D)
>>>
>>> I.e. add dash (-) to make Make ignore failure there.
>>
>> Any progress on this front and instructions how I can install notmuch
>> via homebrew? After the update to Maverick I am "notmuch-less"...
>
> This could work. I don't have Mac so I cannot test
>
> diff --git a/Makefile.local b/Makefile.local
> index 72524eb..b59e063 100644
> --- a/Makefile.local
> +++ b/Makefile.local
> @@ -236,11 +236,11 @@ endif
>  quiet ?= $($(shell echo $1 | sed -e s'/ .*//'))
>  
>  %.o: %.cc $(global_deps)
> -	@mkdir -p .deps/$(@D)
> +	@-mkdir -p .deps .deps/$(@D)
>  	$(call quiet,CXX $(CPPFLAGS) $(CXXFLAGS)) -c $(FINAL_CXXFLAGS) $< -o $@ -MD -MP -MF .deps/$*.d
>  
>  %.o: %.c $(global_deps)
> -	@mkdir -p .deps/$(@D)
> +	@-mkdir -p .deps .deps/$(@D)
>  	$(call quiet,CC $(CPPFLAGS) $(CFLAGS)) -c $(FINAL_CFLAGS) $< -o $@ -MD -MP -MF .deps/$*.d
>  
>  .PHONY : clean
>

Hi Tomi

thanks for the immediate reply, but I am effectively clueless how I can
apply this patch under homebrew.

Any tips appreciated,

Rainer


>
>
>
>>
>> Rainer
>>
>>>
>>>> Michael
>>>
>>> Tomi
>>
>>
>> -- 
>> Rainer M. Krug
>>
>> email: RMKrug<at>gmail<dot>com
>>
>> _______________________________________________
>> notmuch mailing list
>> notmuch@notmuchmail.org
>> http://notmuchmail.org/mailman/listinfo/notmuch
<#secure method=pgpmime mode=sign>

-- 
Rainer M. Krug

email: RMKrug<at>gmail<dot>com

  reply	other threads:[~2013-11-02 16:07 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-25 20:54 Build broken on OS X 10.9 Tad
2013-10-26  9:35 ` Jani Nikula
2013-11-01  1:05   ` Michael Phillips
2013-11-01  6:44     ` Tomi Ollila
2013-11-01 14:02       ` Michael Phillips
2013-11-01 14:22         ` Tomi Ollila
2013-11-02 15:55           ` Rainer M Krug
2013-11-02 16:00             ` Tomi Ollila
2013-11-02 16:07               ` Rainer M Krug [this message]
2013-11-02 17:26                 ` David Bremner
2013-11-07 14:07                   ` Rainer M Krug
2013-11-02 21:08               ` Tomi Ollila

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2iowa949d.fsf@krugs.de \
    --to=rainer@krugs.de \
    --cc=notmuch@notmuchmail.org \
    /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://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).