Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-09-06 Thread Michael Meskes
On Wed, Aug 30, 2006 at 12:48:55PM -0400, Chris Browne wrote: > > This looks like you're using an old version of the parser. preproc.y was > > changed to handle empty database names and the the error you report is > > due to an empty db name. > > I think the problem is that the latest version of p

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-31 Thread Tom Lane
Chris Browne <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] (Tom Lane) writes: >> No, because those derived files are not in CVS at all. What you >> are describing sounds to me like a clock skew problem. Is your >> machine's system clock showing the correct date? > Odd, odd. NOT a clock proble

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-31 Thread Chris Browne
[EMAIL PROTECTED] (Tom Lane) writes: > Chris Browne <[EMAIL PROTECTED]> writes: >> If I touch preproc.y and pgc.l, the .c files get regenerated, and all >> is well. > >> If I don't, they get left alone, and I see compilation errors. > >> It seems to me you need to rebuild the C files and commit the

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-30 Thread Tom Lane
Chris Browne <[EMAIL PROTECTED]> writes: > If I touch preproc.y and pgc.l, the .c files get regenerated, and all > is well. > If I don't, they get left alone, and I see compilation errors. > It seems to me you need to rebuild the C files and commit them. No, because those derived files are not i

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-30 Thread Chris Browne
[EMAIL PROTECTED] (Michael Meskes) writes: > On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: >> >Ah. So this would have caused a bunch of problems in compiling >> >src/interfaces/ecpg/test/connect/test1.pgc??? > > Not the compilation errors I would think. > >> i'm seeing this error

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-30 Thread Jaime Casanova
On 8/30/06, Michael Meskes <[EMAIL PROTECTED]> wrote: On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: > i'm seeing this error when compiling HEAD (updated at ago 29 15:16) > ... This looks like you're using an old version of the parser. preproc.y was changed to handle empty datab

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-30 Thread Michael Meskes
On Tue, Aug 29, 2006 at 03:35:14PM -0500, Jaime Casanova wrote: > >Ah. So this would have caused a bunch of problems in compiling > >src/interfaces/ecpg/test/connect/test1.pgc??? Not the compilation errors I would think. > i'm seeing this error when compiling HEAD (updated at ago 29 15:16) > ...

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-29 Thread Jaime Casanova
On 8/29/06, Chris Browne <[EMAIL PROTECTED]> wrote: [EMAIL PROTECTED] (Tom Lane) writes: > [EMAIL PROTECTED] (Michael Meskes) writes: >> Second try committing the path changes. > > Ah, this looks better. I get clean passes on both HPPA in-tree and > Fedora x86_64 VPATH builds, so I think you've

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-29 Thread Chris Browne
[EMAIL PROTECTED] (Tom Lane) writes: > [EMAIL PROTECTED] (Michael Meskes) writes: >> Second try committing the path changes. > > Ah, this looks better. I get clean passes on both HPPA in-tree and > Fedora x86_64 VPATH builds, so I think you've finally fixed all the > issues. Congrats! Ah. So th

Re: [HACKERS] [COMMITTERS] pgsql: Second try committing the path changes.

2006-08-29 Thread Tom Lane
[EMAIL PROTECTED] (Michael Meskes) writes: > Second try committing the path changes. Ah, this looks better. I get clean passes on both HPPA in-tree and Fedora x86_64 VPATH builds, so I think you've finally fixed all the issues. Congrats! regards, tom lane --