Re: Error on compile for Windows

From: Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Bernard Grosperrin <bgrosperrin(at)laposte(dot)net>, pgsql-general(at)postgresql(dot)org
Subject: Re: Error on compile for Windows
Date: 2009-11-02 06:11:05
Message-ID: 4AEE77F9.7080002@postnewspapers.com.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On 2/11/2009 11:40 AM, Tom Lane wrote:
> "Bernard Grosperrin" <bgrosperrin(at)laposte(dot)net> writes:
>> I have setup a build environment on Windows 7 32 bits, with Visual Studio
>> 2005. Took me a while to get all the bits and parts working, but I finally
>> went through it. Only problem, I get 2 LINK errors:
>> fatal error LINK 1104: cannot open file
>> '.\Release\utf8_and_shift_jis_2004\utf8_and_shift_jis_2004.obj'
>> fatal error LINK 1104: cannot open file
>> '.\Release\euc_jis_2004_and_shift_jis_2004\
>> euc_jis_2004_and_shift_jis_2004.obj'
>
> Hm, do you have a file
>
> src/backend/utils/mb/conversion_procs/euc_jis_2004_and_shift_jis_2004/euc_jis_2004_and_shift_jis_2004.c
>
> and did anything get built from that?
>
> We have seen reports of certain versions of "tar" failing to extract
> this file from the source tarball, probably because its name is so
> long. That could have happened to you --- if so, the recommendation
> is to find another tool to un-tar with.

I almost wonder if a `configure' test to detect this particular form of
source tree corruption would be helpful.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2009-11-02 06:19:16 Re: Error on compile for Windows
Previous Message Tom Lane 2009-11-02 03:40:29 Re: Error on compile for Windows

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2009-11-02 06:19:16 Re: Error on compile for Windows
Previous Message Nikhil Sontakke 2009-11-02 06:02:07 Re: Syntax for partitioning