Re: pgsql: Add transforms feature

Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> ... I'm confused why prairiedog is complaining
> about that. According to Internet lore, this flag seems to be available
> from OS X either 10.3 or 10.1. prairiedog is listed as 10.4, but errors
> with
> MACOSX_DEPLOYMENT_TARGET environment variable set to: 10.1
> Some of the above-mentioned other projects appear to have some OS X
> version test, so we could do something like that. But before we embark
> on that, could you clarify whether the build farm entry lists the
> correct version?

So far as that goes, prairiedog is definitely running OS X 10.4.11.
I cannot find any sign that MACOSX_DEPLOYMENT_TARGET is explicitly set
anywhere. I resorted to grepping the entire filesystem, and found no
smoking gun but a few suggestive hits:

Binary file /usr/bin/ld matches
Binary file /usr/bin/powerpc-apple-darwin8-g++-4.0.1 matches
Binary file /usr/bin/powerpc-apple-darwin8-gcc-4.0.1 matches
/usr/share/aclocal/libtool.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/aclocal/libtool.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/aclocal/libtool.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/acinclude.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/acinclude.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/acinclude.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/aclocal.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/aclocal.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/aclocal.m4: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/configure: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/configure: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/configure: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/configure: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in
/usr/share/libtool/libltdl/configure: case "${MACOSX_DEPLOYMENT_TARGET-10.1}" in

This would explain libtool & libltdl defaulting to 10.1, but I wouldn't
have thought that we use either of those tools. Still, the file dates
on these files are comparable to the file dates on gcc and ld (viz late
2005/early 2006, which matches the window in which Tiger was current).
It would not be terribly surprising if there is an equivalent default
version assumption buried in those executables.

In short then, my best guess is that the 10.4-era build tools defaulted
to building 10.1-compatible product files unless you explicitly override
that by setting MACOSX_DEPLOYMENT_TARGET, which I haven't.

regards, tom lane