The latest version (1.0.2.18) does not conatin bitcode about openssl HOT 28 CLOSED

Xcode 11.3
Deployment Target - iOS 11.1
Configuration - Release

from openssl.

Hi @krzyzanowskim, I have the exact same problem as @chamitha, any suggestions?

Using Xcode 11.1 (stuck with it because of one library), target 12.4.

Thank you

I had the same problem
According to the observation, 1.0.2.20 can be build on xcode11.5, and error build on xcode11.3.1

from openssl.

it never has. Nothing changed in that matter since 1.0.2.17 afaik

from openssl.

it never has. Nothing changed in that matter since 1.0.2.17 afaik

It seems that 1.0.2.18 uses OpenSSL.framework while 1.0.2.17 uses static libs (libcrypto.a & libssl.a)

from openssl.

Fixed on master. Can you plase confirm on your side that the current master 015d226 is ok now?

from openssl.

015d226 has both framework and libs. The compiler still complains no bitcode on the OpenSSL.framework

from openssl.

has both framework and libs.

this is expected. You can use either.

from openssl.

has both framework and libs.

this is expected. You can use either.

I am using this from CocoaPods ... which auto configures and links both the framework file and .a files into the xcode project, and will always cause a linking error.

If there will be difficuties on bitcode into the framework file, maybe we can just roll back to only use .a files, like what 1.2.0.17 does?

from openssl.

which auto configures and links both the framework

ok. this is unexpected then. there is OpenSSL-Universal that uses static libraries and OpenSSL-Universal/Framework that uses framework. I didn't anticipate it will link both

from openssl.

I updated podspec configuration. Static is default now. You need clear pod cache to fetch update version

from openssl.

It works now 👍

from openssl.

I have the same issue on 1.0.2.19 while 1.0.2.18 and ..17 work fine: NordicSemiconductor/IOS-nRF-Mesh-Library#191
However, with those 2 versions I'm unable to push my library to CocoaPod (works with 1.0.2.19).

Here's the log from pod lib lint in my library:

> nRFMeshProvision (2.0.0)
    - ERROR | [iOS] xcodebuild: Returned an unsuccessful exit code. You can use `--verbose` for more information.
    - NOTE  | xcodebuild:  note: Using new build system
    - NOTE  | [iOS] xcodebuild:  note: Planning build
    - NOTE  | [iOS] xcodebuild:  note: Constructing build description
    - NOTE  | [iOS] xcodebuild:  warning: Skipping code signing because the target does not have an Info.plist file and one is not being generated automatically. (in target 'App' from project 'App')
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:314:5: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:330:5: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:487:22: error: a parameter list without types is only allowed in a function definition
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:535:1: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:535:39: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:536:1: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:536:33: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:537:28: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:538:28: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:539:28: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:540:28: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:541:1: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:557:37: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:596:24: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:914:1: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:914:27: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:914:47: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:915:27: error: unknown type name 'BN_ULONG'
    - ERROR | [iOS] xcodebuild:  Headers/Public/OpenSSL-Universal/openssl/bn.h:916:1: error: unknown type name 'BN_ULONG'
    - NOTE  | [iOS] xcodebuild:  fatal error: too many errors emitted, stopping now [-ferror-limit=]

from openssl.

@philips77 Did you clear pod cache to fetch update version?

from openssl.

I think so.
I assume I should use 1.0.2.19, as this is the latest one. As it works for my library and the sample app, should I do pod cache clean OpenSSL-Universal in the test project (which depends on my library), or in my library, as it has been build with some invalid version?
Could you help me with this?

I have 2 project:

1. nRFMeshProvision library (development) with Sample app, released on CocaPods as version 2 with dependency to OpenSSL 1.0.2.19.
2. Test project, that adds dependency to nRFMeshProvision (latest version).

The first one is working fine, at least for me. The second one fails with the error form the 1st post in this issue.

Here's my pod file for the test project:

target 'Test' do
    platform :ios, 13.0
    pod 'nRFMeshProvision'
end

I also tried this:

target 'Test' do
    platform :ios, 13.0
    pod 'nRFMeshProvision', :git => 'https://github.com/NordicSemiconductor/IOS-nRF-Mesh-Library.git', :branch => 'openssl/1.0.2.19'
end

from openssl.

Btw, I just notice a difference in the error message:

ld: '/Users/alno/Desktop/Kaczka/Test/Pods/OpenSSL-Universal/ios/lib/libcrypto.a(cmac.o)' does not contain bitcode. You must rebuild it with bitcode enabled (Xcode setting ENABLE_BITCODE), obtain an updated library from the vendor, or disable bitcode for this target. for architecture arm64

from openssl.

rm -rf ~/Library/Caches/CocoaPods
cd Project
rm Pods

yes, you should use 1.0.2.19, unless something specifies different version.

from openssl.

@philips77 I'm not sure what's going on exactly with "Kaczka" :)
Here's what you can do:

1. Disable bitcode for your app like the message says
2. There's OpenSSL-Universal/Framework that you can try too

from openssl.

Oh, after disabling bitcode in the Kaczka/Test app it compiled successfully. Why does it work with bitcode enabled with older versions?
For the option 2, I would have to change the dependency in my library in podspec, correct? Not in the test app.

from openssl.

Kaczka is a perfect name for anything that can be removed without hesitation. There is no way anything else creates a folder or a file with kaczka in the name, so even 5 years later I know it was me who did this and it's just taking space. Don't want to go to politics ;) but anything with Kaczka can be deleted safely.

from openssl.

Don't want to go to politics ;) but anything with Kaczka can be deleted safely.

did I trigger something by accident? :) I couldn't care less about your project name haha

from openssl.

Oh, after disabling bitcode in the Kaczka/Test app it compiled successfully. Why does it work with bitcode enabled with older versions?

I'm not sure. I'd say it never worked, as bitcode never really worked.

from openssl.

Ok, Thanks for super quick help!

from openssl.

The same issue exists for 1.0.2.19. Is there a solution besides disabling bitcode?

from openssl.

Try 1.0.2.20 and let me know if it worked for you

from openssl.

I get a linker error in Xcode when using 1.0.2.20.

Undefined symbols for architecture arm64:
  "___darwin_check_fd_set_overflow", referenced from:
      _RAND_poll in libcrypto.a(rand_unix.o)
ld: symbol(s) not found for architecture arm64

1.0.2.18 works fine.

from openssl.

What Xcode version do you use, and what deployment target?

from openssl.

Hi @krzyzanowskim, I have the exact same problem as @chamitha, any suggestions?

Using Xcode 11.1 (stuck with it because of one library), target 12.4.

Thank you

from openssl.

I can confirm 1.0.2.19 works as expected with Xcode 11.5 👍

from openssl.