Re: Fix for MSVC header installation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Dave Page <dpage(at)postgresql(dot)org>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, Magnus Hagander <magnus(at)hagander(dot)net>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Fix for MSVC header installation
Date: 2007-04-25 20:56:46
Message-ID: 5796.1177534606@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Dave Page <dpage(at)postgresql(dot)org> writes:
> And we really should make VC++ install in the same locations as mingw by
> default anyway.

I think you guys may be misinterpreting what's happening: this behavior
is not platform-sensitive, it is path-sensitive. In particular, the
configure script will interpolate /postgresql into some of the
installation paths unless the given path already contains "postgres"
or "pgsql". On some of my machines I build working versions into
/home/postgres, and there I get paths like
/home/postgres/version82/share/timezone/...
and on others I build into /home/tgl and get paths like
/home/tgl/version82/share/postgresql/timezone/...

So what I think is happening is that Magnus is getting fooled by which
username he builds under. The thing to standardize on is the full
path you want the stuff to install in (and make sure it doesn't mention
postgres twice).

regards, tom lane

In response to

Responses

Browse pgsql-patches by date

  From Date Subject
Next Message Heikki Linnakangas 2007-04-25 21:14:17 Re: BUG #3245: PANIC: failed to re-find shared loc k o b j ect
Previous Message Dave Page 2007-04-25 19:31:16 Re: Fix for MSVC header installation