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:36:30 -0400 [thread overview]
Message-ID: <50226B5E.9090605@windriver.com> (raw)
In-Reply-To: <1344432356.23275.247.camel@phil-desktop>
On 12-08-08 09:25 AM, Phil Blundell wrote:
> On Wed, 2012-08-08 at 09:24 -0400, Yao Zhao wrote:
>> I want both libz.a and libz.so* in /lib.
>>
>> I wrote a simple test case:
>> cat Makefile
>> all:
>> gcc -c -fPIC -DPIC -o test.o test.c -g
>> gcc -o libtest.so -shared test.o
>> gcc -c -o test_main.o test_main.c -g
>> ar rc libtest.a test.o
>> mv libtest.a usr/lib
>> mv libtest.so lib
>> gcc -o test_main_static test_main.o -L./usr/lib -L./lib -ltest
>> gcc -o test_main_shared test_main.o -L./lib -L./usr/lib -ltest
>>
>> If don't install to same directory then it will have problems.
> That testcase isn't terribly representative since you have libtest.so
> being the actual shared library. In the zlib case, since it has a
> proper SONAME, libz.so.1 and libz.so are distinct.
Slightly modified:
cat Makefile
all:
gcc -c -fPIC -DPIC -o test.o test.c -g
gcc -o libtest.so.1.2 -Wl,-soname,libtest.so.1 -shared test.o
gcc -c -o test_main.o test_main.c -g
ar rc libtest.a test.o
ln -s libtest.so.1.2 libtest.so.1
ln -s libtest.so.1.2 libtest.so
mv libtest.a usr/lib
mv libtest.so* lib
gcc -o test_main_static test_main.o -L./usr/lib -L./lib -ltest
gcc -o test_main_shared test_main.o -Llib -L./usr/lib -ltest
yao
> p.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2012-08-08 13:48 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 [this message]
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=50226B5E.9090605@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