From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] swig: use a relative path for the host swig2.0 symlink's target
Date: Mon, 16 Nov 2015 21:07:53 +0100 [thread overview]
Message-ID: <564A3799.4010407@mind.be> (raw)
In-Reply-To: <1447669504-10777-1-git-send-email-phil@zankapfel.net>
On 16-11-15 11:25, Phil Eichinger wrote:
> An absolute path isn't really necessary and breaks relocating
>
> Signed-off-by: Phil Eichinger <phil@zankapfel.net>
Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
(untested)
Regards,
Arnout
> ---
> package/swig/swig.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/swig/swig.mk b/package/swig/swig.mk
> index 3f3ab2f..6b9b8ae 100644
> --- a/package/swig/swig.mk
> +++ b/package/swig/swig.mk
> @@ -25,7 +25,7 @@ SWIG_LICENSE_FILES = LICENSE LICENSE-GPL LICENSE-UNIVERSITIES
> # swig, so that our swig always gets used.
>
> define HOST_SWIG_INSTALL_SYMLINK
> - ln -fs $(HOST_DIR)/usr/bin/swig $(HOST_DIR)/usr/bin/swig$(SWIG_VERSION_MAJOR)
> + ln -fs swig $(HOST_DIR)/usr/bin/swig$(SWIG_VERSION_MAJOR)
> endef
>
> HOST_SWIG_POST_INSTALL_HOOKS += HOST_SWIG_INSTALL_SYMLINK
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7493 020B C7E3 8618 8DEC 222C 82EB F404 F9AC 0DDF
next prev parent reply other threads:[~2015-11-16 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 10:25 [Buildroot] [PATCH 1/1] swig: use a relative path for the host swig2.0 symlink's target Phil Eichinger
2015-11-16 20:07 ` Arnout Vandecappelle [this message]
2015-11-16 20:27 ` Thomas Petazzoni
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=564A3799.4010407@mind.be \
--to=arnout@mind.be \
--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