Re: Compile error with MSVC - Mailing list pgsql-patches

From Magnus Hagander
Subject Re: Compile error with MSVC
Date
Msg-id 468E1874.2040104@hagander.net
Whole thread Raw
In response to Re: Compile error with MSVC  (Yoshiyuki Asaba <y-asaba@sraoss.co.jp>)
Responses Re: Compile error with MSVC
List pgsql-patches
Yoshiyuki Asaba wrote:
> Hi,
>
> From: Magnus Hagander <magnus@hagander.net>
> Subject: Re: [PATCHES] Compile error with MSVC
> Date: Thu, 05 Jul 2007 07:03:11 +0200
>
>>> I tried to compile using Visual C++ 2005. But I got the following
>>> errors.
>>>
>>>   .\src\backend\parser\keywords.c(22) : fatal error C1083: 'parser/parse.h': No such file or directory
>>>
>>> I saw src/tools/msvc/pgbison.bat. Why does it copy
>>> src/backend/parser/parser.h to src/include/parser directory?
>> <snip>
>> While your solution may be correct (I don't recall offhand how, but it
>> doesn't seem off the chart), I don't see how it can help you in this
>> case. Since pgbison would copy the file there, ISTM that pgbison must
>> have filed. Did you not get a warning output from that one earlier in
>> your build?
>
> If gram.c is older than gram.y, pgbison copy parse.h by custom build
> step. But it is newer, pgbison is skipped.
>
> I see the same problem in PostgreSQL 8.2.4. parse.h does not exist in
> "src/include/parser" directory.

Oh, I see, you're building from the tarball, not from cvs. Now I see the
problem. And yeah, your solution looks like the correct one. I'll take a
look at the details and make sure it gets in there.

//Magnus

pgsql-patches by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: script binaries renaming
Next
From: "Dave Page"
Date:
Subject: Re: script binaries renaming