mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] [PATCH 6/8 v3] [x86_64, multilib] Install Util-linux-ng libraries at the right place
Date: Sun, 25 Mar 2012 12:51:39 +0200	[thread overview]
Message-ID: <20120325105139.GC27119@pengutronix.de> (raw)
In-Reply-To: <1332616028-32312-6-git-send-email-linux@bohmer.net>

On Sat, Mar 24, 2012 at 08:07:06PM +0100, Remy Bohmer wrote:
> Notice that CROSS_AUTOCONF_USR contains --libdir=/usr/lib{,64} setting.
> We want this library in /lib{,64} so we override this setting here
> explicitly.

Does it break anything if we don't do this? I don't think anybody ever
cared what ends up in / and what in /usr. I wouldn't mind installing these
in /usr/lib.

Michael

> Signed-off-by: Remy Bohmer <linux@bohmer.net>
> ---
>  v2: no changes since v1
>  v3: no changes since v2
> 
>  rules/util-linux-ng.make |    1 +
>  1 files changed, 1 insertions(+), 0 deletions(-)
> 
> diff --git a/rules/util-linux-ng.make b/rules/util-linux-ng.make
> index d9a3651..45bb9c2 100644
> --- a/rules/util-linux-ng.make
> +++ b/rules/util-linux-ng.make
> @@ -45,6 +45,7 @@ UTIL_LINUX_NG_ENV 	:= \
>  #
>  UTIL_LINUX_NG_AUTOCONF := \
>  	$(CROSS_AUTOCONF_USR) \
> +	--libdir=/$(CROSS_LIB_DIR) \
>  	--enable-shared \
>  	--disable-static \
>  	--disable-gtk-doc \
> -- 
> 1.7.5.4
> 
> 
> -- 
> ptxdist mailing list
> ptxdist@pengutronix.de
> 

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

  reply	other threads:[~2012-03-25 10:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-24 19:07 [ptxdist] [PATCH 1/8 v3] [x86_64] libgcc need to be install in /lib64 instead of /lib Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 2/8 v3] [x86_64, multilib] Remove all hardcoded paths from glibc.make Remy Bohmer
2012-03-25 11:01   ` Michael Olbrich
2012-03-25 17:34     ` Remy Bohmer
2012-03-26  8:44       ` Michael Olbrich
2012-03-26 10:09         ` Remy Bohmer
2012-03-27  6:23           ` Michael Olbrich
2012-03-27  7:18             ` Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 3/8 v3] [x86_64, multilib] Make packages install their libraries at the right place Remy Bohmer
2012-03-25 10:25   ` Michael Olbrich
2012-03-25 10:41     ` Remy Bohmer
2012-03-25 17:43       ` Remy Bohmer
2012-03-25 18:11         ` Remy Bohmer
2012-03-27 14:09           ` Michael Olbrich
2012-03-24 19:07 ` [ptxdist] [PATCH 4/8 v3] [x86_64, multilib] Install Zlib " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 5/8 v3] [x86_64, multilib] Install Ncurses " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 6/8 v3] [x86_64, multilib] Install Util-linux-ng " Remy Bohmer
2012-03-25 10:51   ` Michael Olbrich [this message]
2012-03-25 10:55     ` Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 7/8 v3] [x86_64, multilib] Install Readline " Remy Bohmer
2012-03-24 19:07 ` [ptxdist] [PATCH 8/8 v3] [x86_64, multilib] Install Procps " Remy Bohmer

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=20120325105139.GC27119@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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