Re: [EXT] Re: Building "Fat" Mac Binary, or Cross-Compiling from ARM arch to x86-64

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



I hear you. But given that there are two (or three at most!) architectures – I fail to see why building one complicated package with guaranteed 50% garbage (x86 machines don’t need PPC or AARCH64, and vs. versa) would be better than building two (or three) straightforward packages, one for each architecture, with no fluff.

 

--

V/R,

Uri

 

There are two ways to design a system. One is to make it so simple there are obviously no deficiencies.

The other is to make it so complex there are no obvious deficiencies.

                                                                                                                                     -  C. A. R. Hoare

 

 

From: 'Mounir IDRASSI' via openssl-users <openssl-users@xxxxxxxxxxx>
Date: Friday, January 3, 2025 at 04:16
To: openssl-users@xxxxxxxxxxx <openssl-users@xxxxxxxxxxx>
Subject: Re: [EXT] Re: Building "Fat" Mac Binary, or Cross-Compiling from ARM arch to x86-64

!-------------------------------------------------------------------|
  This Message Is From an External Sender
  This message came from outside the Laboratory.
|-------------------------------------------------------------------!

On 1/3/2025 3:01 AM, Blumenthal, Uri - 0553 - MITLL wrote:
> In my experience, it’s been _never_ useful to build “fat” binaries.
> They brought nothing but problems.
>
> In our place we build x86_64 binaries for Intel, and AARCH64 for
> Silicon - and is been perfectly satisfactory here. I recommend
> considering the same (proven) approach.

On my side, using "fat" binaries on macOS for OpenSSL linked products
has been a positive experience.
I have been using this approach for various macOS products since Mac OS
X Tiger to provide single installation packages that target all
architectures (including ppc, i386).
Of course, it depends on the type and complexity of the application
logic but usually it is possible to sort out issues without much
difficulty, and OpenSSL is almost never the cause of any issues.

--
Mounir IDRASSI


--
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe@xxxxxxxxxxx.
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/a9a300d1-fe63-48ae-b38e-ea4bd1aacc1c%40idrix.net.

--
You received this message because you are subscribed to the Google Groups "openssl-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to openssl-users+unsubscribe@xxxxxxxxxxx.
To view this discussion visit https://groups.google.com/a/openssl.org/d/msgid/openssl-users/BN0P110MB1419443472B6D4308E675DC09015A%40BN0P110MB1419.NAMP110.PROD.OUTLOOK.COM.

Attachment: smime.p7s
Description: S/MIME cryptographic signature


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [ECOS]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux