Assuming you're talking about OS X, it wasn't last time I looked into it.
curlbuild.h differed.

What we do is build one with -arch x86_64, copy curlbuild.h to
curlbuild64.h, build one with -arch i386, copy curlbuild.h to
curlbuild32.h, lipo the libraries together, then create a new curlbuild.h

cat > include/curl/curlbuild.h <<EOF
#ifdef __LP64__
#include "curlbuild64.h"
#else
#include "curlbuild32.h"
#endif
EOF

This still works in our build system. I have not revisited it to determine
whether it's still necessary.

Geoff

On Thu, Aug 27, 2015 at 6:43 PM, Jeffrey Walton <noloader_at_gmail.com> wrote:

> Hi Everyone,
>
> A quick question (Google did not produce a useful hit).
>
> Is it safe to build the cURL library as multi-arch? In particular:
>
> export CFLAGS="-arch ppc -arch ppc64"
> ./configure ...
>
> If the headers are agnostic, then I think it should be safe. (A
> library like OpenSSL cannot be safely built like this because of the
> configuration/architecture settings in <openssl/opensslconf.h>).
>
> Are there any architecture dependent settings or defines written to a
> header?
>
> Thanks in advance.
> -------------------------------------------------------------------
> List admin: http://cool.haxx.se/list/listinfo/curl-library
> Etiquette: http://curl.haxx.se/mail/etiquette.html

-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2015-08-28