mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Remy Bohmer <linux@bohmer.net>
To: ptxdist@pengutronix.de, Michael Olbrich <m.olbrich@pengutronix.de>
Subject: [ptxdist] [PATCH 4/6 v5] [x86_64, multilib] Install Zlib libraries at the right place
Date: Wed, 28 Mar 2012 21:05:03 +0200	[thread overview]
Message-ID: <1332961505-16641-4-git-send-email-linux@bohmer.net> (raw)
In-Reply-To: <1332961505-16641-1-git-send-email-linux@bohmer.net>

Signed-off-by: Remy Bohmer <linux@bohmer.net>
---
 v5: No changes compared to v4

 rules/zlib.make |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)

diff --git a/rules/zlib.make b/rules/zlib.make
index 1618e1b..2c15ccb 100644
--- a/rules/zlib.make
+++ b/rules/zlib.make
@@ -48,7 +48,8 @@ ZLIB_CONF_ENV := \
 #
 ZLIB_AUTOCONF := \
 	--prefix=/usr \
-	--uname=Linux
+	--uname=Linux \
+	--libdir=/usr/$(CROSS_LIB_DIR)
 
 ifdef PTXCONF_ZLIB_STATIC
 ZLIB_AUTOCONF += --static
-- 
1.7.5.4


-- 
ptxdist mailing list
ptxdist@pengutronix.de

  parent reply	other threads:[~2012-03-28 19:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-28 19:05 [ptxdist] [PATCH 1/6 v5] [x86_64, multilib] libgcc need to be install in /lib64 instead of /lib Remy Bohmer
2012-03-28 19:05 ` [ptxdist] [PATCH 2/6 v5] [x86_64, multilib] Remove hardcoded paths from glibc.make Remy Bohmer
2012-03-28 19:05 ` [ptxdist] [PATCH 3/6 v5] [x86_64, multilib] Make packages install their libraries at the right place Remy Bohmer
2012-03-28 19:05 ` Remy Bohmer [this message]
2012-03-28 19:05 ` [ptxdist] [PATCH 5/6 v5] [x86_64, multilib] Install Ncurses " Remy Bohmer
2012-03-28 19:05 ` [ptxdist] [PATCH 6/6 v5] [x86_64, multilib] Install Procps " Remy Bohmer
2012-04-04  6:21 ` [ptxdist] [PATCH 1/6 v5] [x86_64, multilib] libgcc need to be install in /lib64 instead of /lib Michael Olbrich

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=1332961505-16641-4-git-send-email-linux@bohmer.net \
    --to=linux@bohmer.net \
    --cc=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