All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Elder <aelder@sgi.com>
To: Bill Kendall <wkendall@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: fix xfs_invutil dependency generation
Date: Mon, 29 Nov 2010 14:48:57 -0600	[thread overview]
Message-ID: <1291063737.2425.13.camel@doink> (raw)
In-Reply-To: <20101129163424.GA22014@sgi.com>

On Mon, 2010-11-29 at 10:34 -0600, Bill Kendall wrote:
> Correct the target name for dependency generation in the
> invutil Makefile. This is now consistent with other dump
> makefiles and eliminates "No such file or directory"
> errors during the build.
> 
> Signed-off-by: Bill Kendall <wkendall@sgi.com>

Looks good.

Reviewed-by: Alex Elder <aelder@sgi.com>

> ---
>  invutil/Makefile |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Index: xfsdump-kernel.org/invutil/Makefile
> ===================================================================
> --- xfsdump-kernel.org.orig/invutil/Makefile
> +++ xfsdump-kernel.org/invutil/Makefile
> @@ -70,7 +70,7 @@ install: default
>  	$(LTINSTALL) -m 755 $(LTCOMMAND) $(PKG_SBIN_DIR)
>  install-dev:
>  
> -depend: $(COMMINCL) $(COMMON) $(INVINCL) $(INVCOMMON)
> +.dep: $(COMMINCL) $(COMMON) $(INVINCL) $(INVCOMMON)
>  
>  $(COMMINCL) $(COMMON):
>  	@echo "    [LN]     $@"
> 
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs



_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

      reply	other threads:[~2010-11-29 20:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-29 16:34 [PATCH] xfsdump: fix xfs_invutil dependency generation Bill Kendall
2010-11-29 20:48 ` Alex Elder [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=1291063737.2425.13.camel@doink \
    --to=aelder@sgi.com \
    --cc=wkendall@sgi.com \
    --cc=xfs@oss.sgi.com \
    /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.