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

[Andrew Koenig]

Phil> Oh, absolutely.  I use the LD_RUN_PATH choice myself.

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

I am trying to avoid editing any of the distribution files if I
possibly can, because then I have to understand what has changed
for each new release.

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

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

Ah well, I now have a solution that works for me, so I won't worry too hard
about it.