Re: an installation bug in either gcc, gld, or readline -- I don't know which

[Phil Edwards <pedwards at disaster dot jaj dot com>]

On Wed, Dec 26, 2001 at 08:27:48PM -0500, Andrew Koenig wrote:
> Phil> For Solaris you have the additional options of
> 
> Phil>     4) Use '-Wl,-Rfoo' when linking, to embed 'foo' into the executable
> Phil>        as a directory path to search at runtime.  This will work with both
> Phil>        GNU and Sun ld (with sufficiently recent GNU versions).  E.g.,
> Phil>        -Wl,-R/usr/gnu/lib
> 
> The thing is that someone has to supply that option.  Setting LD_RUN_PATH
> is easier.

Oh, absolutely.  I use the LD_RUN_PATH choice myself.

You could also edit the specs file (see 'gcc -v' output) to make that
"somebody" be the gcc/g++ driver itself.  This would be a system-wide
effect.  Or you could write your own ancilliary specs file, or use a gcc/g++
wrapper script, and so on.


> Phil> In this case, the readline people would have to adopt libtool rather than
> Phil> calling their shobj-conf script.
> 
> Is that likely?

Up to them.  :-)  Autoconf and automake are fairly mature, especially
with 2.50.  Libtool still has some sharp edges, but is improving rapidly.


Phil

-- 
If ye love wealth greater than liberty, the tranquility of servitude greater
than the animating contest for freedom, go home and leave us in peace.  We seek
not your counsel, nor your arms.  Crouch down and lick the hand that feeds you;
and may posterity forget that ye were our countrymen.            - Samuel Adams