Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Derek Buitenhuis <derek.buitenhuis@gmail.com>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx
Date: Tue, 07 Aug 2012 13:39:04 -0400	[thread overview]
Message-ID: <502152B8.6070100@gmail.com> (raw)
In-Reply-To: <1344360704-23172-1-git-send-email-yao.zhao@windriver.com>

On 07/08/2012 1:31 PM, Yao Zhao wrote:
> In order to fix the QA Issue for libpam which installed to /lib but
> reference /usr/libxx/libz and libcrack, install libz and libcrack
> to /lib.

OpenBSD puts libpam.so in /lib, so it seems kosher...

>  do_install() {
> -	oe_runmake DESTDIR=${D} install
> +	#libz.a installs to libdir, overwrite the env libdir
> +	#install pkgconfig to env libdir/pkgconfig
> +	oe_runmake DESTDIR=${D} pkgconfigdir="${libdir}/pkgconfig" \
> +		   libdir="${base_libdir}" install
>  }

If you're specifying --libdir when configuring, why do you need
libdir during make, as well?

- Derek



  reply	other threads:[~2012-08-07 17:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-07 17:31 [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx Yao Zhao
2012-08-07 17:39 ` Derek Buitenhuis [this message]
2012-08-07 18:30   ` Yao Zhao
2012-08-07 18:30     ` Phil Blundell
2012-08-07 18:35       ` Yao Zhao
2012-08-07 18:38         ` Phil Blundell
2012-08-07 18:43           ` Yao Zhao
2012-08-07 18:45             ` Phil Blundell
2012-08-07 19:29               ` Yao Zhao
2012-08-07 21:20                 ` Phil Blundell
2012-08-08 13:24                   ` Yao Zhao
2012-08-08 13:25                     ` Phil Blundell
2012-08-08 13:36                       ` Yao Zhao
2012-08-07 18:35     ` Derek Buitenhuis
2012-08-08 13:26       ` Yao Zhao
2012-08-07 18:17 ` Koen Kooi

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=502152B8.6070100@gmail.com \
    --to=derek.buitenhuis@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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