Re: [HACKERS] Build failure in current CVS (src/backend/utils/mb/conversion_procs)

2002-08-20 Thread Tom Lane
Tatsuo Ishii <[EMAIL PROTECTED]> writes: > IMO giving a directory to each conversion > is more manageable than putting everything in single directory. I lean towards Peter's point here. One or two files per conversion is not unmanageable to keep in a single directory. And I have noticed that "m

Re: [HACKERS] Build failure in current CVS (src/backend/utils/mb/conversion_procs)

2002-08-20 Thread Peter Eisentraut
Tom Lane writes: > John Gray <[EMAIL PROTECTED]> writes: > > I get the following when I attempt to build outside of the source tree. > > It looks like the new stuff for loadable conversion modules is not > correct for building outside the source tree; it's being careless about > the paths it uses

Re: [HACKERS] Build failure in current CVS (src/backend/utils/mb/conversion_procs)

2002-08-20 Thread Tom Lane
John Gray <[EMAIL PROTECTED]> writes: > I get the following when I attempt to build outside of the source tree. It looks like the new stuff for loadable conversion modules is not correct for building outside the source tree; it's being careless about the paths it uses to find files. Tatsuo, can

[HACKERS] Build failure in current CVS (src/backend/utils/mb/conversion_procs)

2002-08-20 Thread John Gray
Hi all, I get the following when I attempt to build outside of the source tree. All goes well until make[4]: Entering directory `/home/jgray/postgres/pg-build/src/backend/utils/mb/conversion_procs/ascii_and_mic' Makefile:11: ../proc.mk: No such file or directory make[4]: *** No rule to make