From: Martin Bochnig <mb1x@gmx.com>
To: sol10x86@cox.net, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] configure flag for compilation question..
Date: Sat, 14 Oct 2006 02:21:03 +0200 [thread overview]
Message-ID: <45302D6F.1010708@gmx.com> (raw)
In-Reply-To: <21180689.1160782036071.JavaMail.root@eastrmwml08.mgt.cox.net>
Ben Taylor wrote:
>---- Ishwar Rattan <ishwar@pali.cps.cmich.edu> wrote:
>
>
>>On Fri, 13 Oct 2006, Martin Bochnig wrote:
>>
>>
>>
>>>Ishwar Rattan wrote:
>>>
>>>
>>>
>>>Where is the problem 64bit versus 32bit ?
>>>(32 bit version of libSDL-1.2.so.0 found while amd64 64bit version needed?)
>>>(should go under /usr/local/lib/amd64/libSDL-1.2.so.0)
>>>
>>>
>>Well, the problem is I do not root privileges so can't place libSL in
>>/usr/local/lib or /usr/local/lib/amd64.
>>
>>I would like to keep it in $HOME/lib and want qemu to see the lib
>>archive.
>>
>>I will try LD_LIBRARY_PATH option.
>>
>>
>
>It should work. the main thing is to not to agressive with LD_LIBRARY_PATH in
>this case. Since it sounds like it already may be linking against /usr/local/lib
>where the current libSDL is, you should just be able to add the new lib dir
>to the LD_LIBRARY_PATH env variable, and then run ldd on qemu to make
>sure it's finding the right libraries. When you have the right LD_LIBRARY_PATH,
>then it should be working for you.
>
>
>
>>Is to possible to have a staticly
>>linked version of libSDL in the qemu binaries?
>>
>>
>
>There is an option for statically linked libSDL in the qemu binaries,
>
>
Sounds funny.
>and I tried to make sure I kept that intact for solaris in the configure
>script.
>
wow
>Try it and see what happens.
>
>
Not much.
>Ben
>
>
>_______________________________________________
>Qemu-devel mailing list
>Qemu-devel@nongnu.org
>http://lists.nongnu.org/mailman/listinfo/qemu-devel
>
>
>
>
next prev parent reply other threads:[~2006-10-14 0:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-13 23:27 [Qemu-devel] configure flag for compilation question Ben Taylor
2006-10-14 0:21 ` Martin Bochnig [this message]
-- strict thread matches above, loose matches on Subject: below --
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-13 19:30 ` Martin Bochnig
2006-10-13 20:16 ` 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=45302D6F.1010708@gmx.com \
--to=mb1x@gmx.com \
--cc=qemu-devel@nongnu.org \
--cc=sol10x86@cox.net \
/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).