Re: cannot get build (initdb) to work after trying for a week

(list re-added)

you need a timezone directory, not just timezonesets. So your problem is
why that's not being installed when you do "make install". You need to
check the output from the "make install" command to see if there are any
errors or warnings related to that. (It's done when make install reaches
the src/timezone directory)

The PATH should have nothing to do with it.

//Magnus

Eric Fish wrote:
> Thanks. I just compared my Mac and PC installations. Mac installation
> (which works correctly) and has a bunch of entries, including other
> directories, under share/postgresql/timezone. The PC installation (which
> doesn't work) has a directory share/timezonesets with similar, but far fewer
> entries (all .txt files).
>
> Also tried prior to running initdb:
>
> export TZ=PST
>
> which didn't work either.
>
> Was thinking that maybe it's my PATH on Windows that could be fouling things
> up. I added the necessary bin dirs for pg and msys/mingw but have all types
> of MS items in the path too (which would be difficult to clean out). But
> I'm wondering if that's it.
>
> -----Original Message-----
> From: Magnus Hagander [mailto:magnus(at)hagander(dot)net]
> Sent: Sunday, March 18, 2007 7:11 AM
> To: Eric
> Cc: pgsql-general(at)postgresql(dot)org
> Subject: Re: [GENERAL] cannot get build (initdb) to work after trying for a
> week
>
> Eric wrote:
>> I am getting truly desperate! I am trying to build any version of
>> Postgres on Windows from source. First experience with Postgres
>> source. I have struggled for days trying to solve a problem. Would be
>> willing to pay for the solution!!!
>>
>> The following error occurred when issuing a vanilla initdb command on
>> my Windows system.
>>
>> FATAL: could not select a suitable default timezone
>> DETAIL: It appears that your GMT time zone uses leap seconds.
>> PostgreSQL does not support leap seconds.
>>
>> I built this from 8.1.8 source under msys/mingw. Also tried 8.2.2.
>> Everything builds fine but initdb always reports the above error and
>> quits.
>
> This could happen if the timezone files aren't properly installed. This
> should normally happen when you do "make install", but verify that they
> are actually present (in share/timezone).
>
>> I also had to create a typedef int ssize_t in a couple of files to get
>> the compile finished. Maybe this is related. Other than that, have
>> not touched any code.
>
> I don't think that's related, but it's a clear indicator that something
> in your environment is broken. Because it should build without any such
> changes.
>
> //Magnus