Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Yao Zhao <yao.zhao@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cracklib, zlib: install to /lib instead of /usr/libxx
Date: Wed, 8 Aug 2012 09:26:50 -0400	[thread overview]
Message-ID: <5022691A.9010800@windriver.com> (raw)
In-Reply-To: <50215FE3.5060205@gmail.com>

On 12-08-07 02:35 PM, Derek Buitenhuis wrote:
> On 07/08/2012 2:30 PM, Yao Zhao wrote:
>> zlib is not using autotools although it has configure.
>> when install, oe_runmake will be make -e so Makefile will always use
>> env's libdir which is the usr/libxx, we have to overwrite it when install.
> Perhaps you don't need to specify during configure then? :shrug:
That is true.
But this makes Makefile clearer and for non oe distribution it is 
supposed to change here and will work.
The hack in install part is for oe only.

yao
> - Derek
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core





  reply	other threads:[~2012-08-08 13:38 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
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 [this message]
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=5022691A.9010800@windriver.com \
    --to=yao.zhao@windriver.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