From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Subject: | Re: Getting to universal binaries for Darwin |
Date: | 2008-07-20 07:50:36 |
Message-ID: | 200807201050.37558.peter_e@gmx.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Am Sunday, 20. July 2008 schrieb Tom Lane:
> * This disables AC_TRY_RUN tests, of course. The only adverse
> consequence I noticed was failure to recognize that
> -Wl,-dead_strip_dylibs is applicable, which is marginally annoying but
> hardly fatal.
>
> On the whole I still wouldn't trust cross-compiled configure results.
> Better to get your prototype pg_config.h from the real deal.
For example, I'm a bit curious on the following aspect. This program should
fail to compile on 32-bit platforms but succeed on 64-bit:
#include <stddef.h>
struct s { char a; long b; };
int main(int argc, char *argv[])
{
int array[offsetof(struct s, b) - 5];
return 0;
}
What happens if you run gcc -arch i386 -arch ppp64 on it? Does it require
success on both output architectures?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-07-20 13:48:15 | Re: Getting to universal binaries for Darwin |
Previous Message | Simon Riggs | 2008-07-20 06:37:42 | Re: pg_dump additional options for performance |