pi'll causes longer orgasms

2005-02-20 Thread Shelly Marshall

Increase your SPERM V0LUME, and Orgasm Length
main benifits:
- The longest most intense Orgasms of your life
- Erctions like steel
- lncreased libido/desire
- Stronger ejaculaton (watch where your aiming)
- Multiple 0rgasms
- Up to 5OO% more volume (cover her in it if you want)
- Studies show it tastes sweeter
DlSCREET SAME DAY SHlPPlNG - TRY lT, YOU'LL L0VE IT!
(and she'll thank you for it)

0ptout:
http://rz3e23fzf.com/dd.php




___
http://lists.gnu.org/mailman/listinfo/libtool


I still do not know how to use -rpath with libtool+automake

2005-02-20 Thread Bruce Korb

Hi,

This should be really simple.  I find it extraordinarily difficult.
I have a project that has a library and an executable.  When I
run the executable, it needs to get externals resolved against
the library in the build tree, not the installed version.  So far,
my various attempts break things in one way or another.  Usually,
I do not see problems, because the installed library is sufficient
for my test environment.

In order to work, libtool must be given the -rpath option at
link time.  If I put ``-rpath $(libdir)'' into the LDFLAGS
automake variable for the program, I still do not get the effect
I need.  If I put it in LDADD, I get complaints.  If I use
``-Wl,-R$(libdir)'' then the installed library shows up too soon.
If I leave this stuff off, then the build executable has to have
LD_LIBRARY_PATH set in order to function properly.

OK.  That's what is frustrating.  Here's what I want:

I would very much like to know exactly what strings to put into which
Automake variables in order to have the build tree variation of
my program find the build tree variation of the library and then have
the installed version of the program find the installed library
*WITHOUT* having to resort to manual intervention with LD_LIBRARY_PATH.

If this is documented in the .texi manual, then it seems to not be
indexed in a way I can find it.  It may be because the Automake manual
does not cover libtool very well and, conversely, libtool doesn't cover
the Automake usage very well.

So, summarized again slightly differently:  I understand how to invoke
libtool to create a shell script wrapped executable that finds the right
library.  I do not understand how to tell Automake to do the same thing.
Thank you for your kind help.  - Bruce



___
http://lists.gnu.org/mailman/listinfo/libtool


Re: I still do not know how to use -rpath with libtool+automake

2005-02-20 Thread Bob Friesenhahn
On Sun, 20 Feb 2005, Bruce Korb wrote:
This should be really simple.  I find it extraordinarily difficult.
I have a project that has a library and an executable.  When I
run the executable, it needs to get externals resolved against
the library in the build tree, not the installed version.  So far,
Normally libtool's generated wrapper script causes the uninstalled 
library to be used.  If this is not the case, then there is a bug.

If the system supports LD_LIBRARY_PATH, then it should be used via the 
wrapper script.  Otherwise the libraries and dependent programs need 
to be re-linked during the install phase, which is slow and clunky, 
and might even fail.  The method used is part of libtool's own 
configuration mechanism, and I don't think that you can alter it 
without modifying libtool itself.

Use './libtool --config' to see all of the configuration options that 
libtool selected for your system.  Short descriptions are included.

Bob
==
Bob Friesenhahn
[EMAIL PROTECTED], http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,http://www.GraphicsMagick.org/
___
http://lists.gnu.org/mailman/listinfo/libtool