| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Ordering problem with --with-includes |
| Date: | 2001-02-19 23:36:03 |
| Message-ID: | 3952.982625763@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2001-02-19 23:40:45 | Re: [HACKERS] Re: v7.1b4 bad performance |
| Previous Message | Hiroshi Inoue | 2001-02-19 23:28:47 | Re: [HACKERS] Re: v7.1b4 bad performance |