From: Martin Bochnig <mb1x@gmx.com>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] configure flag for compilation question..
Date: Fri, 13 Oct 2006 21:30:55 +0200 [thread overview]
Message-ID: <452FE96F.1020800@gmx.com> (raw)
In-Reply-To: <12993045.1160767103427.JavaMail.root@eastrmwml08.mgt.cox.net>
Ben Taylor wrote:
>---- Ishwar Rattan <ishwar@pali.cps.cmich.edu> wrote:
>
>
>>Trying to compile qemu on amd64 based Solaris.
>>
>>I do not have write permission to /usr/local subtree
>>
>>./configure --libdir=other-path --prefix=not-ustlocal
>>is fine
>>but make always generates binaries that want to find
>>/usr/local/lib/libSDL-1.2.so.0 etc. (checked with ldd).
>>
>>What is the way out for this sticky point?
>>
>>
>
>Manually add "-L/usr/local/lib -R/usr/local/lib"
>
Rather "-L/his/home/sdl_amd64/lib -R/his/home/sdl_amd64/lib"
Because I doubt, an amd64 version of libSDL is currently present in
/usr/local/lib/amd64
(and he doesn't have w access).
This method is btw not really "new" to me, see my posting from a few
hours ago:
http://www.opensolaris.org/jive/thread.jspa?threadID=15448&tstart=0
>to the Makefile for the link
>phase so it will correctly add those paths to the library lookup. If I had
>a code base to look at this instance, I could tell you where. You could
>also add those flags to Makefile.target in the SOLARIS specific areas,
>which would probably make more sense.
>
>As Martin indicated, setting LD_LIBRARY_PATH may get you a running
>binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.
>
>Ben
>
>
> "LD_LIBRARY_PATH is the wrong answer for Solaris"
???
--->> Weak statement.
It has its [dis]advantages.
Namely that the paths to a library are _not_ hardwired.
That's the exactly reason, why I did recommend it in this very scenario.
And I would do it again for Ishwar's current needs.
-M.
next prev parent reply other threads:[~2006-10-13 19:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 19:18 [Qemu-devel] configure flag for compilation question Ben Taylor
2006-10-13 19:30 ` Martin Bochnig [this message]
2006-10-13 20:16 ` Martin Bochnig
-- strict thread matches above, loose matches on Subject: below --
2006-10-13 23:27 Ben Taylor
2006-10-14 0:21 ` Martin Bochnig
2006-10-13 23:22 Ben Taylor
2006-10-14 5:23 ` Martin Bochnig
2006-10-13 23:03 Ben Taylor
2006-10-13 23:10 ` Martin Bochnig
2006-10-13 19:18 Ben Taylor
2006-10-16 21:41 ` Ishwar Rattan
2006-10-13 18:18 Ishwar Rattan
2006-10-13 18:52 ` Martin Bochnig
2006-10-13 18:48 ` Ishwar Rattan
2006-10-13 19:11 ` Martin Bochnig
2006-10-13 19:17 ` Ishwar Rattan
2006-10-13 19:39 ` Martin Bochnig
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=452FE96F.1020800@gmx.com \
--to=mb1x@gmx.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).