qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Ben Taylor <sol10x86@cox.net>
To: Martin Bochnig <mb1x@gmx.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] configure flag for compilation question..
Date: Fri, 13 Oct 2006 19:03:33 -0400	[thread overview]
Message-ID: <12457496.1160780613485.JavaMail.root@eastrmwml08.mgt.cox.net> (raw)


---- Martin Bochnig <mb1x@gmx.com> wrote: 
> Ben Taylor wrote:
> 
> >As Martin indicated, setting LD_LIBRARY_PATH may get you a running
> >binary, but LD_LIBRARY_PATH is the wrong answer for Solaris.
> >
> >  
> >
> 
> My answer had been a bit longer:
> 
> "Read ld.so.1(1)
> i.e.
> # man ld.so.1
> 
> Then: *One* option is to set $LD_LIBRARY_PATH (or potentially
> $LD_LIBRARY_PATH_64 [not required])."

I'm not saying it doesn't work.  But properly compiled programs for
Solaris include the run time paths to the libraries so an LD_LIBRARY_PATH
environment variable is not required.

LD_LIBRARY_PATH is interesting to test out new versions of support
libraries without actually having to recompile, so it has it's uses.
but too often, folks use LD_LIBRARY_PATH as a panacea on Solaris
to fix poorly compiled programs.

Ben

             reply	other threads:[~2006-10-13 23:03 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-13 23:03 Ben Taylor [this message]
2006-10-13 23:10 ` [Qemu-devel] configure flag for compilation question 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 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=12457496.1160780613485.JavaMail.root@eastrmwml08.mgt.cox.net \
    --to=sol10x86@cox.net \
    --cc=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).