Re: specifying readline location & ignoring libdir...?

[L A Walsh]

Chet Ramey wrote:
> On 11/16/16 12:48 PM, L A Walsh wrote:
>
>   
> > ---
> >    I suspected as much, which makes these settings all the
> > more important ... these 2 things:
> >
> >
> >    1) How is the location for readline-7.0 specified?
> >     
>
> Using the --with-installed-readline argument to `configure'. 
---
   I note that readline puts the .a files in the top level, but
the ".so" files are in a subdir, "shlib".  Which location
would be needed by the 'installed-readline' option?

   But maybe more importantly, why does the link step ignore
the value of libdir used by configure (specified by the --libdir=<dir>
argument).

   Also,  does the link step look for the version it wants, or
does it leave the version unspecified.  I'm not sure of the syntax
for ".a", but for .so's it would look like:


For example:
>  \ls -lgG /lib64/libread*|cut -c34-
/lib64/libreadline.so -> libreadline.so.6
/lib64/libreadline.so.6 -> libreadline.so.6.2
/lib64/libreadline.so.6.2
/lib64/libreadline.so.7 -> libreadline.so.7.0
/lib64/libreadline.so.7.0

If a prog only needs major version 7, it would look
for ".so.7" first, then try the less specific ".so"
file next.


> RL_LIBDIR
> and
> RL_LIBSRC
>
> which are the build and source directories for your local version of
> readline, respectively.
>   
---
   That might be the best workaround in the near term,
but fixing the build procedure to use the dir specified by
the --libdir arg to configure would really be better in the
long term...

-Linda