>>
>> In log2 I got the same errors as I mentioned earlier:
>> LOG: could not open directory "/home/<build-path>/.../share/timezone": No such file or directory
>> ... ...
> Does it really have a pathname with three dots here?
>
> I'd have more confidence we knew what we were looking at if you sent
> the actual log, rather than an edited version of the lines you think
> are most important.
>
And why the heck use initdb's -L? initdb knows quite well where to get
its files from, if you haven't mucked up the installation. I don't think
I've ever seen a case in production where it's been necessary.
-------------------------------------
1) The pathnames referenced in the log do not have any dots, I just truncated them - they are absolute pathnames to
wherethe timezone files are locates in the source or build tree I'll post the entire log if it is still needed after
this...
2) We have been using 'initdb -L' since Postgres 7.2 The way it works here we build Postgres and it gets bundled as a
partof a larger application, which can be installed anywhere. Perhaps this makes it difficult for initdb to "know
quitewell where to get its files from".
If I remove the -L switch initdb breaks very early before it gets to the timezones: share_path points back to the
buildlocation, which is not available, so it cannot locate postgres.bki and other input files.
The timezones piece seems to be the only problem - if I compile with --with-system-tzdata=/usr/share/zoneinfo
andthen use initdb -L installation succeeds when the source/build tree is not accessible. Not claiming any
knowledgein this area - would it be reasonable to expect that if -L option works for other input files it should
alsowork for timezones?
Thanks for all your help
This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and
maybe confidential and/or privileged. If you are not one of the named recipients or have received this email in error,
(i)you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this
emailand all attachments, (iii) Dassault Systemes does not accept or assume any liability or responsibility for any use
ofor reliance on this email.For other languages, go to http://www.3ds.com/terms/email-disclaimer.