public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Franck Bui-Huu <vagabon.xyz@gmail.com>
To: linux-sh@vger.kernel.org
Subject: [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks
Date: Mon, 17 Mar 2008 19:25:08 +0000	[thread overview]
Message-ID: <47DEC594.6010502@gmail.com> (raw)

From: Franck Bui-Huu <fbuihuu@gmail.com>

Usually relative paths are preferred because they survive directory
moves, work across networked file systems/chrooted environments.

And in this case, there's no point to use absolute paths.

Signed-off-by: Franck Bui-Huu <fbuihuu@gmail.com>
---
 arch/sh/Makefile |    7 +++----
 1 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/arch/sh/Makefile b/arch/sh/Makefile
index c510c22..14b39b1 100644
--- a/arch/sh/Makefile
+++ b/arch/sh/Makefile
@@ -164,7 +164,7 @@ include/asm-sh/.cpu: $(wildcard include/config/cpu/*.h) \
 		     include/config/auto.conf FORCE
 	@echo '  SYMLINK include/asm-sh/cpu -> include/asm-sh/$(cpuincdir-y)'
 	$(Q)if [ ! -d include/asm-sh ]; then mkdir -p include/asm-sh; fi
-	$(Q)ln -fsn $(incdir-prefix)$(cpuincdir-y) include/asm-sh/cpu
+	$(Q)ln -fsn $(cpuincdir-y) include/asm-sh/cpu
 	@touch $@
 
 #	Most boards have their own mach directories.  For the ones that
@@ -185,13 +185,12 @@ include/asm-sh/.mach: $(wildcard include/config/sh/*.h) \
 	if [ -d $(incdir-prefix)$$i ]; then \
 		echo -n '  SYMLINK include/asm-sh/mach -> '; \
 		echo -e "include/asm-sh/$$i"; \
-		ln -fsn $(incdir-prefix)$$i \
-			include/asm-sh/mach; \
+		ln -fsn $$i include/asm-sh/mach; \
 	else \
 		if [ ! -d include/asm-sh/mach ]; then \
 			echo -n '  SYMLINK include/asm-sh/mach -> '; \
 			echo -e 'include/asm-sh'; \
-			ln -fsn $(incdir-prefix) include/asm-sh/mach; \
+			ln -fsn ../asm-sh include/asm-sh/mach; \
 		fi; \
 	fi; \
 	done
-- 
1.5.4.4.GIT


             reply	other threads:[~2008-03-17 19:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-17 19:25 Franck Bui-Huu [this message]
2008-03-17 19:51 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} Stuart MENEFY
2008-03-18  3:11 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Paul Mundt
2008-03-18  7:26 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} Franck Bui-Huu
2008-03-18  7:31 ` Franck Bui-Huu
2008-03-18 19:04 ` Franck Bui-Huu
2008-03-21  3:39 ` [PATCH] Use relative path when creating include/asm/{mach,cpu} symlinks Paul Mundt

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=47DEC594.6010502@gmail.com \
    --to=vagabon.xyz@gmail.com \
    --cc=linux-sh@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox