From: "Wang, Jian J" <jian.j.wang@intel.com>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>,
"lersek@redhat.com" <lersek@redhat.com>
Cc: "Bi, Dandan" <dandan.bi@intel.com>, "Lu, XiaoyuX" <xiaoyux.lu@intel.com>
Subject: Re: [edk2-devel] [PATCH] CryptoPkg/OpensslLib: fix VS2017 build failure
Date: Wed, 5 Jun 2019 14:25:17 +0000 [thread overview]
Message-ID: <D827630B58408649ACB04F44C510003625910E9B@SHSMSX107.ccr.corp.intel.com> (raw)
In-Reply-To: <0c1baf42-58c8-e5fe-ed38-8c4728337944@redhat.com>
Laszlo,
> -----Original Message-----
> From: devel@edk2.groups.io [mailto:devel@edk2.groups.io] On Behalf Of
> Laszlo Ersek
> Sent: Wednesday, June 05, 2019 7:00 PM
> To: devel@edk2.groups.io; Wang, Jian J <jian.j.wang@intel.com>
> Cc: Bi, Dandan <dandan.bi@intel.com>; Lu, XiaoyuX <xiaoyux.lu@intel.com>
> Subject: Re: [edk2-devel] [PATCH] CryptoPkg/OpensslLib: fix VS2017 build failure
>
> Hi Jian,
>
> On 06/04/19 23:18, Wang, Jian J wrote:
> > BZ: https://bugzilla.tianocore.org/show_bug.cgi?id=1878
> >
> > This issue is specific to VS2017 which tries to resolve symbol referenced
> > by a symbol not really referenced eventually.
> >
> > ossl_init_load_crypto_strings
> > -> err_load_crypto_strings_int (not really referenced)
> > -> ERR_load_OSSL_STORE_strings
> >
> > Because OPENSSL_NO_ERR and OPENSSL_NO_AUTOERRINIT are not defined
> by
> > default, err_load_crypto_strings_int() will not be actually referenced
> > by ossl_init_load_crypto_strings().
> >
> > Since err_load_crypto_strings_int() is not actually referenced at all,
> > the fix can be done simply by removing crypto/err/err_all.c from build.
> >
> > Cc: Dandan Bi <dandan.bi@intel.com>
> > Cc: Xiaoyu Lu <xiaoyux.lu@intel.com>
> > Signed-off-by: Jian J Wang <jian.j.wang@intel.com>
> > ---
> > CryptoPkg/Library/OpensslLib/OpensslLib.inf | 1 -
> > CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf | 1 -
> > 2 files changed, 2 deletions(-)
> >
> > diff --git a/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> > index 378fa6588e..5a2424fc16 100644
> > --- a/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> > +++ b/CryptoPkg/Library/OpensslLib/OpensslLib.inf
> > @@ -218,7 +218,6 @@
> > $(OPENSSL_PATH)/crypto/dso/dso_win32.c
> > $(OPENSSL_PATH)/crypto/ebcdic.c
> > $(OPENSSL_PATH)/crypto/err/err.c
> > - $(OPENSSL_PATH)/crypto/err/err_all.c
> > $(OPENSSL_PATH)/crypto/err/err_prn.c
> > $(OPENSSL_PATH)/crypto/evp/bio_b64.c
> > $(OPENSSL_PATH)/crypto/evp/bio_enc.c
> > diff --git a/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf
> b/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf
> > index 24d3d96459..588da4c040 100644
> > --- a/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf
> > +++ b/CryptoPkg/Library/OpensslLib/OpensslLibCrypto.inf
> > @@ -218,7 +218,6 @@
> > $(OPENSSL_PATH)/crypto/dso/dso_win32.c
> > $(OPENSSL_PATH)/crypto/ebcdic.c
> > $(OPENSSL_PATH)/crypto/err/err.c
> > - $(OPENSSL_PATH)/crypto/err/err_all.c
> > $(OPENSSL_PATH)/crypto/err/err_prn.c
> > $(OPENSSL_PATH)/crypto/evp/bio_b64.c
> > $(OPENSSL_PATH)/crypto/evp/bio_enc.c
> >
>
> after the edk2-stable201905 tag, we might want to update
> "CryptoPkg/Library/OpensslLib/process_files.pl" as well, to exclude this
> file. In order to fix the build issue for the stable tag, this patch is
> acceptable (I see it's been pushed already, and that's fine); but in the
> longer term, we should not manually update the section that's marked as
> "Autogenerated files list starts here".
>
> If you agree, can you please file a TianoCore BZ about this? (I.e.
> special handling for "err_all.c" in "process_files.pl".)
>
Agree. The fix is a bit rush. A BZ has been filed. Thanks for catching it.
https://bugzilla.tianocore.org/show_bug.cgi?id=1881
Regards,
Jian
> Thanks
> Laszlo
>
>
prev parent reply other threads:[~2019-06-05 14:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-04 21:18 [PATCH] CryptoPkg/OpensslLib: fix VS2017 build failure Wang, Jian J
2019-06-05 0:22 ` [edk2-devel] " Liming Gao
[not found] ` <15A525952F820008.28502@groups.io>
2019-06-05 8:23 ` Liming Gao
2019-06-05 11:00 ` Laszlo Ersek
2019-06-05 14:25 ` Wang, Jian J [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=D827630B58408649ACB04F44C510003625910E9B@SHSMSX107.ccr.corp.intel.com \
--to=devel@edk2.groups.io \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox