/usr/local/include search
Why don't we search in /usr/local/include and /usr/local/lib for
libreadline.a by default, and require the flags to configure?
Seems we should have those directories searched by default in configure.
Most software does this with configure already.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
Bruce Momjian <maillist@candle.pha.pa.us> writes:
Why don't we search in /usr/local/include and /usr/local/lib for
libreadline.a by default, and require the flags to configure?
I'm pretty leery of having configure make unsupported assumptions
about the layout of my filesystem. Not everyone keeps this sort
of thing in /usr/local, and it's *not* necessarily harmless to look
there without being told. For example, /usr/local might contain
libraries that are incompatible with the compiler you're trying to
use --- I actually had that problem a few weeks ago when I was
experimenting with egcs.
I think it's fine that configure defaults to looking only in whatever
directories the compiler searches automatically. gcc, for one, is
usually configured to search in /usr/local by default, so the whole
issue is moot for anyone using gcc.
regards, tom lane
Import Notes
Reply to msg id not found: YourmessageofSat19Jun1999231944-0400199906200319.XAA12279@candle.pha.pa.us | Resolved by subject fallback