From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
Cc: | Magnus Hagander <mha(at)sollentuna(dot)net>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: pgxs/windows |
Date: | 2006-01-15 22:02:54 |
Message-ID: | 17092.1137362574@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Andrew Dunstan <andrew(at)dunslane(dot)net> writes:
> I doubt DESTDIR is having an effect. From what I can see we hardly use
> it so it will mostly be blank:
Yes, it is often an empty string, which doubtless explains how an error
of this sort could sneak in. But I think there's no doubt that one or
the other of those definitions is wrong. I'm not completely sure which
though. DESTDIR should be included if we are referencing the
installation tree at build time, but perhaps not for post-install
purposes, which is the environment that PGXS should deal with.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Andrew Dunstan | 2006-01-15 23:02:30 | Re: pgxs/windows |
Previous Message | Andrew Dunstan | 2006-01-15 21:56:52 | Re: pgxs/windows |
From | Date | Subject | |
---|---|---|---|
Next Message | Neil Conway | 2006-01-15 22:23:05 | Re: inferred param types for PREPARE |
Previous Message | Andrew Dunstan | 2006-01-15 21:56:52 | Re: pgxs/windows |