I appreciate you and other guys who has been working for this
problem.
--
Tatsuo Ishii
> Thanks. Fixed. I had a '[' on the first line of one of the makefiles.
> ---
>
> Neil Conway wrote:
> > Bruce Momjian <[EMAIL PROTECT
Thanks. Fixed. I had a '[' on the first line of one of the makefiles.
---
Neil Conway wrote:
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, patch applied to all Makefiles, as outlined by Peter.
>
> I see this in cur
IL PROTECTED]; [EMAIL PROTECTED]
> Subject: Re: [HACKERS] Build failure in current CVS
>
>
> Bruce Momjian <[EMAIL PROTECTED]> writes:
> > OK, patch applied to all Makefiles, as outlined by Peter.
>
> I see this in current CVS:
>
> make[3]: Entering directory
>
Bruce Momjian <[EMAIL PROTECTED]> writes:
> OK, patch applied to all Makefiles, as outlined by Peter.
I see this in current CVS:
make[3]: Entering directory `/home/nconway/pgsql/src/backend/utils/mb/conversion_procs'
make[4]: Entering directory
`/home/nconway/pgsql/src/backend/utils/mb/conversi
OK, patch applied to all Makefiles, as outlined by Peter.
---
Peter Eisentraut wrote:
> Tatsuo Ishii writes:
>
> > I have applied following changes and am getting:
> >
> > make: *** No rule to make target `ascii_and_mic.o'
Tatsuo Ishii writes:
> I have applied following changes and am getting:
>
> make: *** No rule to make target `ascii_and_mic.o', needed by
>`libascii_and_mic.so.0.0'. Stop.
>
> under one of a conversion directory. The weird thing is I do not get
> this if I do a build "inside" the source tree. A
> 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 you fix that, or ask Peter
> for help?
I have applied following changes and am getting:
make: *** No rule
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
> Tatsuo, why is there one directory per encoding combination with only one
> source file each? Couldn't we put all the files in one directory?
euc_tw_and_big5 has *two* files. Also Unicode mapping files could be
moved to each directory. So the Unicode related functions might have
one more file.
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
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
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
12 matches
Mail list logo
