Re: Problems with win32 patch/build - Mailing list pgsql-hackers

From Merlin Moncure
Subject Re: Problems with win32 patch/build
Date
Msg-id 303E00EBDD07B943924382E153890E5433F803@cuthbert.rcsinc.local
Whole thread Raw
In response to Problems with win32 patch/build  ("Merlin Moncure" <merlin.moncure@rcsonline.com>)
List pgsql-hackers
> I am working my way through getting the postgres win32 port (7.2.1)
> compiled under MSVC.  I got through the patch and the compilation, but
> am having problems with the linker.  Trying to link the backend, I get
> 43 linker errors like:
> unresolved external symbol GUC-scanstr
> unresolved external symbol ProcessConfigFile
> unresolved external symbol num_columns_read
> unresolved external symbol Int_yychar
>
> These symbols are listed in the postgres.def file.  Removing them
> removes the errors.  If I do so, I get a new set of errors:
>
> Linking...
>    Creating library ..\..\Debug/postgres.lib and object
> ..\..\Debug/postgres.exp
> postmaster.obj : error LNK2001: unresolved external symbol
> _ProcessConfigFile
> bootstrap.lib(bootstrap.obj) : error LNK2001: unresolved external
symbol
> _ProcessConfigFile
> tcop.lib(postgres.obj) : error LNK2001: unresolved external symbol
> _ProcessConfigFile
> bootstrap.lib(bootstrap.obj) : error LNK2001: unresolved external
symbol
> _Int_yyparse
> ..\..\Debug\backend.dll : fatal error LNK1120: 2 unresolved externals
> Error executing link.exe
>
>
> Also, when trying to compile ecpg, I get
> flex: could not create '.\preproc\pgc.c'
>
> There were some weird things that went on during my first compile run
> that I fixed as I went and I'm afraid I broke something.  Any
> suggestions?
>
> If I can get through this I'll start hitting patch #2 and start
running
> tests versus 7.3.x source.

I wrote:

I think I figured it out.  lexx has a problem with the guc_file.l.  I
should be able to tackle that: sorry to pester.

Merlin


pgsql-hackers by date:

Previous
From: "Dave Page"
Date:
Subject: Re: Roadmap for FE/BE protocol redesign
Next
From: "Dave Page"
Date:
Subject: Re: Roadmap for FE/BE protocol redesign