From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] c-icap: avoid host library search path
Date: Wed, 20 Apr 2016 07:31:43 +0300 [thread overview]
Message-ID: <20160420043143.GH2476@tarshish> (raw)
In-Reply-To: <20160419211457.11d9bf2a@free-electrons.com>
Hi Thomas,
On Tue, Apr 19, 2016 at 09:14:57PM +0200, Thomas Petazzoni wrote:
> On Tue, 19 Apr 2016 21:15:44 +0300, Baruch Siach wrote:
>
> > +C_ICAP_MAKE_OPTS = exec_prefix=$(STAGING_DIR)/usr
>
> This is not correct. Setting exec_prefix to $(STAGING_DIR)/usr is
> wrong.
Quoting configure:
# Installation directory options.
# These are left unexpanded so users can "make install exec_prefix=/foo"
# and all the variables that are supposed to be based on exec_prefix
# by default will actually change.
> Instead, can you try to remove:
>
> -rpath @libdir@
>
> from the various Makefile.am ?
I can do that, but I'm not sure upstream would like it.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -
next prev parent reply other threads:[~2016-04-20 4:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-19 18:15 [Buildroot] [PATCH 1/3] c-icap: avoid host library search path Baruch Siach
2016-04-19 18:15 ` [Buildroot] [PATCH 2/3] c-icap: bump to version 0.4.2 Baruch Siach
2016-04-19 19:16 ` Thomas Petazzoni
2016-04-20 4:28 ` Baruch Siach
2016-04-20 8:06 ` Thomas Petazzoni
2016-04-19 18:15 ` [Buildroot] [PATCH 3/3] c-icap-modules: " Baruch Siach
2016-04-19 19:14 ` [Buildroot] [PATCH 1/3] c-icap: avoid host library search path Thomas Petazzoni
2016-04-20 4:31 ` Baruch Siach [this message]
2016-04-20 18:04 ` Baruch Siach
2016-04-20 19:20 ` Thomas Petazzoni
2016-04-20 19:37 ` Baruch Siach
2016-04-20 21:35 ` Arnout Vandecappelle
2016-04-21 6:58 ` Baruch Siach
2016-04-21 13:17 ` Arnout Vandecappelle
2016-04-19 21:53 ` Arnout Vandecappelle
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=20160420043143.GH2476@tarshish \
--to=baruch@tkos.co.il \
--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 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.