Skip to content

Work around BoringSSL bitcode linker warning#470

Merged
keith merged 4 commits intomasterfrom
ks/work-around-boringssl-bitcode-linker-warning
Oct 1, 2019
Merged

Work around BoringSSL bitcode linker warning#470
keith merged 4 commits intomasterfrom
ks/work-around-boringssl-bitcode-linker-warning

Conversation

@keith
Copy link
Copy Markdown
Member

@keith keith commented Sep 28, 2019

When linking envoy-mobile to an iOS app that ships with bitcode, you get
these warnings from the linker:

ld: warning: Linker asked to preserve internal global: 'sk_CRYPTO_BUFFER_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'

I have submitted an upstream patch to fix this
https://boringssl-review.googlesource.com/c/boringssl/+/37804 in the
meantime I've applied that patch here.

Signed-off-by: Keith Smiley keithbsmiley@gmail.com

When linking envoy-mobile to an iOS app that ships with bitcode, you get
these warnings from the linker:

```
ld: warning: Linker asked to preserve internal global: 'sk_CRYPTO_BUFFER_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
ld: warning: Linker asked to preserve internal global: 'sk_X509_call_free_func'
```

I have submitted an upstream patch to fix this
https://boringssl-review.googlesource.com/c/boringssl/+/37804 in the
meantime I've applied that patch here.

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
rebello95
rebello95 previously approved these changes Sep 28, 2019
Copy link
Copy Markdown
Contributor

@rebello95 rebello95 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind filing an issue in this repo to track this as well? Thanks!!

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@keith
Copy link
Copy Markdown
Member Author

keith commented Sep 28, 2019

#471

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@goaway
Copy link
Copy Markdown
Contributor

goaway commented Sep 30, 2019

thanks @keith!

@keith
Copy link
Copy Markdown
Member Author

keith commented Sep 30, 2019

Lets hold on this until we have some clarity upstream about this fix

Signed-off-by: Keith Smiley <keithbsmiley@gmail.com>
@keith
Copy link
Copy Markdown
Member Author

keith commented Oct 1, 2019

Going to update the upstream conversation but this is fine for now

@keith keith merged commit 80e04e2 into master Oct 1, 2019
@keith keith deleted the ks/work-around-boringssl-bitcode-linker-warning branch October 1, 2019 01:08
alyssawilk added a commit that referenced this pull request Nov 2, 2022
Reverting #470 which is a patch to boringssl
https://boringssl-review.googlesource.com/c/boringssl/+/37804 indicates that this patch was added to avoid a linker error, so given CI passes I assume it can be reverted.

Risk Level: low
Testing: n/a
Docs Changes: n/a
Release Notes: n/a

Part of envoyproxy/envoy#23758
Fixes #471

Signed-off-by: Alyssa Wilk <alyssar@chromium.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants