From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] /usr/local/include search |
Date: | 1999-06-20 15:00:44 |
Message-ID: | 12706.929890844@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 1999-06-20 23:22:39 | Re: [HACKERS] Update on my 6.4.2 progress |
Previous Message | Tom Lane | 1999-06-20 14:51:33 | Re: [HACKERS] tables > 1 gig |