From: "Jérôme Pouiller" <jezz@sysmic.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 4/4] Makefile: staging symlink uses a relative path
Date: Thu, 16 Jul 2015 12:17:36 +0200 [thread overview]
Message-ID: <6195872.eqbV4amuVy@sagittea> (raw)
In-Reply-To: <1436775527-2484-5-git-send-email-s.martin49@gmail.com>
Hello Samuel,
On Monday 13 July 2015 10:18:47 Samuel Martin wrote:
> A step forward toward a relocatable SDK.
>
> Signed-off-by: Samuel Martin <s.martin49@gmail.com>
> ---
> Makefile | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Makefile b/Makefile
> index daf692e..30a2d0e 100644
> --- a/Makefile
> +++ b/Makefile
> @@ -447,7 +447,7 @@ $(STAGING_DIR):
> @ln -snf lib $(STAGING_DIR)/usr/$(LIB_SYMLINK)
> @mkdir -p $(STAGING_DIR)/usr/include
> @mkdir -p $(STAGING_DIR)/usr/bin
> - @ln -snf $(STAGING_DIR) $(BASE_DIR)/staging
> + @ln -snf $(subst $(BASE_DIR)/,,$(STAGING_DIR)) $(BASE_DIR)/staging
Does it work if user customize BR2_HOST_DIR?
BR,
--
J?r?me Pouiller, Sysmic
Embedded Linux specialist
http://www.sysmic.fr
next prev parent reply other threads:[~2015-07-16 10:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 8:18 [Buildroot] [PATCH v2 0/4] Host-package: RPATH fixup Samuel Martin
2015-07-13 8:18 ` [Buildroot] [PATCH v2 1/4] support/scripts: add fix_rpaths Samuel Martin
2015-07-13 8:26 ` Baruch Siach
2015-07-13 8:18 ` [Buildroot] [PATCH v2 2/4] package/patchelf: add HOST_FIX_RPATH_HOOK to TARGET_FINALIZE_HOOKS Samuel Martin
2015-07-13 8:32 ` Baruch Siach
2015-07-13 8:18 ` [Buildroot] [PATCH v2 3/4] package/patchelf: add TARGET_CLEAR_RPATH_HOOK " Samuel Martin
2015-07-13 8:18 ` [Buildroot] [PATCH v2 4/4] Makefile: staging symlink uses a relative path Samuel Martin
2015-07-16 10:17 ` Jérôme Pouiller [this message]
2015-07-19 7:15 ` Samuel Martin
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=6195872.eqbV4amuVy@sagittea \
--to=jezz@sysmic.org \
--cc=buildroot@busybox.net \
/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