Re: problems with readline (compilation on mac fails)

[Ethan A M. <sf...@us...>]

On Monday, February 14, 2011 09:13:31 am Ethan A Merritt wrote:
> On Monday, February 14, 2011 08:23:21 am Mojca Miklavec wrote:
> > On Mon, Feb 14, 2011 at 17:15, Ethan Merritt <merritt@u.washington.edu> wrote:
> > > On Monday, February 14, 2011, Mojca Miklavec wrote:
> > >> Dear list,
> > >>
> > >> if I remove MacPorts from PATH (I had to do it since I have serious
> > >> problems with AquaTerm), building fails with:
> > >>
> > >> plot.c:110:30: error: readline/tilde.h: No such file or directory
> > >> make[3]: *** [plot.o] Error 1
> > >> make[2]: *** [all-recursive] Error 1
> > >> make[1]: *** [all-recursive] Error 1
> > >> make: *** [all] Error 2
> > >>
> > >> I indeed have no tilde.h except in /opt/local/include/readline/tilde.h
> > >> (and in some TeX-related sources).
> > >
> > > The configure script explicitly tests for the presence of support for
> > > tilde expansion in the local readline.  Did you re-run ./configure
> > > after changing your PATH?
> > 
> > Yes, I did. I tried that again. I did "make clean; ./configure
> > --disable-wxwidgets; make".
> > 
> > From config.log:
> > 
> > configure:8168: checking readline/tilde.h usability
> > configure:8168: gcc -c -g -O2 -ObjC   conftest.c >&5
> > conftest.c:133:28: error: readline/tilde.h: No such file or directory
> > configure:8168: $? = 1
> 
> OK, so then config.h should contain a line
> #define MISSING_RL_TILDE_EXPANSION 1
> 
> If it does not, then I conclude that your system is missing the
> equivalent of the -*devel*- package for readline.  I.e., you still have
> the library in your path but you do not have the matching header files
> in your path.
> 
> On the other hand, I am puzzled by the specific line you show from
> config.log, because I don't see any check for "readline/tilde.h usability"
> in the configure script generated from current CVS source for either
> 4.4 or 4.5.  Where did your configure script come from?

And indeed, I now see that the test you quote was present in version 4.2
but was replaced by different, more extensive configuration tests in later
versions.  So I suspect that your configure script is out of date and needs
to be regenerated from current source.
		Ethan