Tom Lane wrote:
Merlin Moncure mmonc...@gmail.com writes:
Noticed another issue with 'client only' type installs in the
Makefile. Shouldn't make install on libpq install postgres_ext.h in
addition to the interface headers?
I don't think libpq's Makefile has any business doing that.
On Wed, Feb 4, 2009 at 1:22 PM, Bruce Momjian br...@momjian.us wrote:
Tom Lane wrote:
Merlin Moncure mmonc...@gmail.com writes:
Noticed another issue with 'client only' type installs in the
Makefile. Shouldn't make install on libpq install postgres_ext.h in
addition to the interface
Did we address this?
---
Merlin Moncure wrote:
On Thu, Nov 6, 2008 at 12:45 PM, Tom Lane t...@sss.pgh.pa.us wrote:
Merlin Moncure mmonc...@gmail.com writes:
IMO, the client only build should be fixed, so we can:
*)
On Thu, Nov 6, 2008 at 12:45 PM, Tom Lane [EMAIL PROTECTED] wrote:
Merlin Moncure [EMAIL PROTECTED] writes:
IMO, the client only build should be fixed, so we can:
*) put the makefile hack I proposed in
*) implement the keywords.c change suggested above
*) set up backend/parser symlink from
Merlin Moncure [EMAIL PROTECTED] writes:
Noticed another issue with 'client only' type installs in the
Makefile. Shouldn't make install on libpq install postgres_ext.h in
addition to the interface headers?
I don't think libpq's Makefile has any business doing that.
Maybe we should bite the
Tom Lane wrote:
Maybe we should bite the bullet and provide some kind of top-level make
targets for client-only build/install.
That would probably work best.
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
I'm trying to do client only builds on a bunch of legacy platforms and
noticed that the include path is messed up...if keywords.o is not
already built, it fails to build be because src/backend/parser but not
src/backend is in the include path. (keywords.c includes
parser/gram.h).
The following
Merlin Moncure [EMAIL PROTECTED] writes:
I'm trying to do client only builds on a bunch of legacy platforms and
noticed that the include path is messed up...if keywords.o is not
already built, it fails to build be because src/backend/parser but not
src/backend is in the include path.
On Thu, Nov 6, 2008 at 11:09 AM, Tom Lane [EMAIL PROTECTED] wrote:
Merlin Moncure [EMAIL PROTECTED] writes:
I'm trying to do client only builds on a bunch of legacy platforms and
noticed that the include path is messed up...if keywords.o is not
already built, it fails to build be because
Merlin Moncure [EMAIL PROTECTED] writes:
This looks caused by a change to clean up
some quoting issues:
No, that patch is unrelated --- it didn't modify the inclusion situation
at all.
regards, tom lane
--
Sent via pgsql-hackers mailing list
On Thu, Nov 6, 2008 at 12:26 PM, Tom Lane [EMAIL PROTECTED] wrote:
Merlin Moncure [EMAIL PROTECTED] writes:
This looks caused by a change to clean up
some quoting issues:
No, that patch is unrelated --- it didn't modify the inclusion situation
at all.
oopright againcvs annotate
Merlin Moncure [EMAIL PROTECTED] writes:
IMO, the client only build should be fixed, so we can:
*) put the makefile hack I proposed in
*) implement the keywords.c change suggested above
*) set up backend/parser symlink from different/additional place.
The last of these seems the correct fix.
12 matches
Mail list logo