building openssl for darwin64-arm64-cc target in a Intel Mac

Tathagata Chakraborty contact.tatha at gmail.com
Thu Jun 22 11:10:36 UTC 2023


There was a typo in the question, flags I used were:

./config --prefix=<path> --openssldir=<path> darwin64-arm64-cc no-asm
no-shared enable-fips .


Thanks,
Tathagata Chakraborty
Mo: 9884869684


On Thu, Jun 22, 2023 at 4:39 PM Tathagata Chakraborty <
contact.tatha at gmail.com> wrote:

> Hi,
>
> I am using an intel 64 bit mac machine and trying to build open SSL with
> fips enabled for two different targets : darwin64-x86_64-cc
> and darwin64-arm64-cc. My x86-64 build works fine, all the make tests
> succeed but darwin64-arm64-cc target build fails. make was a success, but
> it fails in make test. make install also fails. This is because the test
> tries to run fips-install which fails with "bad CPU in executable". I think
> this is because fips install attempts to load the arm binaries (openssl and
> fips.dylib) on an intel platform.
>
> I ran make clean, make distclean after doing Intel build and
> afterwards configured the ARM target with the correct flags :
> ./config --prefix=<path> --openssldir=<path> darwin64-x86_64-cc no-asm
> no-shared enable-fips .
>
> Now I have two questions:
> (1) Is there any recommended way of achieving what I am trying to achieve?
> i.e. build open SSL for arm using an Intel machine?
> (2) The binaries that I have built, is it safe to use them ?
>
> Thanks,
> Tathagata Chakraborty
> Mo: 9884869684
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mta.openssl.org/pipermail/openssl-users/attachments/20230622/411240f8/attachment-0001.htm>


More information about the openssl-users mailing list