From: | Adriaan van Os <postgres(at)microbizz(dot)nl> |
---|---|
To: | pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: Getting to universal binaries for Darwin |
Date: | 2008-07-19 11:35:17 |
Message-ID: | 4881D175.80109@microbizz.nl |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> The bad news is that if you only do that, only the arch that you
> actually build on will work. We have configure set up to insert
> various hardware-dependent definitions into pg_config.h and
> ecpg_config.h, and if you don't have the right values visible for
> each compilation, the resulting executables will fail.
>
> You can get around that by hacking up the generated config files
> with #ifdef __i386__ and so on to expose the correct values of
> the hardware-dependent symbols to each build. Of course you have
> to know what the correct values are --- if you don't have a sample
> of each architecture handy to run configure against, it'd be easy
> to miss some things. And even then it's pretty tedious. I am
> not sure if it is possible or worth the trouble to try to automate
> this part better.
It may be less pain to simply config and build for ppc and i386 in separate build directories and
then glue the resulting binaries together with lipo
<http://developer.apple.com/documentation/Darwin/Reference/ManPages/man1/lipo.1.html> to make them
"universal".
Regards,
Adriaan van Os
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Urbański | 2008-07-19 12:40:59 | Re: gsoc, oprrest function for text search |
Previous Message | Jan Urbański | 2008-07-19 11:15:27 | gsoc, oprrest function for text search |