I find that if one specifies, say,

	configure --with-includes=/usr/local/include

one gets compiler commands like

	cc -Ae -g +z -I/usr/local/include -I../../../src/include -I../../../src/interfaces/libpq  -c -o pgtcl.o pgtcl.c

because the -I commands are added to CPPFLAGS which appears before any
-I commands the makefiles themselves add.  This strikes me as uncool.
For example, it will be impossible to compile Postgres if there are
headers from an old version lurking in /usr/local/include, because those
will be read instead of the ones from our source tree.  How hard would
it be to make the --with-includes -I directives appear after our own?

The same problem arises for --with-libs, btw.

			regards, tom lane

Mon, 19 Feb 2001 18:36:03 -0500
Tom Lane <tgl@sss.pgh.pa.us>
Ordering problem with --with-includes
Tom Lane writes:

> How hard would it be to make the --with-includes -I directives appear
> after our own?

Not hard, but tedious.

> The same problem arises for --with-libs, btw.

Not tedious, but hard.

I'll look into it.

-- 
Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/


Tue, 20 Feb 2001 18:10:11 +0100 (CET)
Peter Eisentraut <peter_e@gmx.net>
Re: Ordering problem with --with-includes