Skip site navigation (1) Skip section navigation (2)

Re: Latest ecpg patch broke MSVC build

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Michael Meskes <meskes(at)postgresql(dot)org>, ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Latest ecpg patch broke MSVC build
Date: 2007-10-01 03:30:35
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers

Tom Lane wrote:
> This morning's ecpg patch certainly seems to have been snake-bit.
> Although the Windows gcc buildfarm members seem happy, the MSVC ones
> are all failing with
> Linking...
>            Creating library Release\libecpg\libecpg.lib and object Release\libecpg\libecpg.exp
>         libecpg.exp : error LNK2001: unresolved external symbol DllMain(at)12
>         .\Release\libecpg\libecpg.dll : fatal error LNK1120: 1 unresolved externals
> I see that DllMain() got added to misc.c, so it's not obvious what's
> wrong here.  Some adjustment needed in the MSVC build scripts maybe?

It is building with thread.c but it should not be unless I am misreading 
the Makefile. The makefile processing in doesn't look nearly 
powerful enough to handle this:

  # thread.c is needed only for non-WIN32 implementation of path.c
  ifneq ($(PORTNAME), win32)
  OBJS += thread.o

It will ignore the if and endif lines and process the OBJS line :-(

A quick fix is probably to put some whitespace in front of "OBJS", 
although that seems horribly fragile.



In response to


pgsql-hackers by date

Next:From: Tom LaneDate: 2007-10-01 03:46:00
Subject: Re: Latest ecpg patch broke MSVC build
Previous:From: Chris BrowneDate: 2007-10-01 02:45:38
Subject: Re: 8.3 beta timing

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group