public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "Laszlo Ersek" <lersek@redhat.com>
To: devel@edk2.groups.io, dwmw2@infradead.org, xiaoyux.lu@intel.com
Cc: Jian J Wang <jian.j.wang@intel.com>, Ting Ye <ting.ye@intel.com>,
	Richard Levitte <levitte@openssl.org>
Subject: Re: [edk2-devel] [PATCH v1 1/1] CryptoPkg/OpensslLib: Exclude err_all.c in process_files.py
Date: Thu, 20 Jun 2019 16:46:54 +0200	[thread overview]
Message-ID: <c6c028b2-2624-ab77-b6fe-ed080cd2cade@redhat.com> (raw)
In-Reply-To: <e23c996cf8908eb2643b7278751151202c8bb57e.camel@infradead.org>

On 06/20/19 09:54, David Woodhouse wrote:
> On Wed, 2019-06-19 at 03:19 -0400, Xiaoyu Lu wrote:
>> REF: https://bugzilla.tianocore.org/show_bug.cgi?id=1881
>>
>> Commit(0a1b13fd4d2210e2c3) fix VS2017 build failure
>> remove useless file in OpensslLib[Crypto].inf,
>> but we use process_files.py to generate files.
>> So exclude err_all.c file in process_files.py
>>
>> Cc: Jian J Wang <jian.j.wang@intel.com>
>> Cc: Ting Ye <ting.ye@intel.com>
>> Signed-off-by: Xiaoyu Lu <xiaoyux.lu@intel.com>
>> ---
>>  CryptoPkg/Library/OpensslLib/process_files.pl | 1 +
>>  1 file changed, 1 insertion(+)
>>
>> diff --git a/CryptoPkg/Library/OpensslLib/process_files.pl b/CryptoPkg/Library/OpensslLib/process_files.pl
>> index e277108f0734..2783ff54f95a 100755
>> --- a/CryptoPkg/Library/OpensslLib/process_files.pl
>> +++ b/CryptoPkg/Library/OpensslLib/process_files.pl
>> @@ -132,6 +132,7 @@ foreach my $product ((@{$unified_info{libraries}},
>>              # So it can reduce porting time, compile time, library size.
>>              next if $s =~ "crypto/rand/randfile.c";
>>              next if $s =~ "crypto/store/";
>> +            next if $s =~ "crypto/err/err_all.c";
>>  
>>              if ($product =~ "libssl") {
>>                  push @sslfilelist, '  $(OPENSSL_PATH)/' . $s . "\r\n";
>> -- 
> 
> Hm, this looks like the wrong approach to me. I only ever meant the
> exclusions here to be a hack, to fix up things we couldn't properly do
> in OpenSSL by disabling features.
> 
> Now if you'd fixed up the crypto/store/ exclusion properly by prodding
> Richard to add an OPENSSL_NO_STORE option, then the subsequent
> inclusion of ERR_load_OSSL_STORE_strings() in err_all.c wouldn't have
> led to further hacks to exclude *that* file...
> 
> Please submit a PR to OpenSSL to add 'no-store' if you really don't
> want it.

I actually agree about "no-store"; please see point (1) in my earlier
review here:

http://mid.mail-archive.com/0c5b5e95-cb2c-75af-a30b-015dac14b91c@redhat.com

But I've run out of steam on this -- especially the last weeks have seen
me struggle with just reading my email. :(

Thanks
Laszlo

  reply	other threads:[~2019-06-20 14:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-19  7:19 [PATCH v1 1/1] CryptoPkg/OpensslLib: Exclude err_all.c in process_files.py Xiaoyu Lu
2019-06-19 22:59 ` Laszlo Ersek
2019-06-20  0:34 ` [edk2-devel] " Wang, Jian J
2019-06-20  7:54 ` David Woodhouse
2019-06-20 14:46   ` Laszlo Ersek [this message]
2019-06-20 22:33     ` David Woodhouse
2019-06-21  8:37       ` Wang, Jian J
2019-06-24 19:54         ` Laszlo Ersek
2019-06-25  8:58           ` Wang, Jian J
2019-06-26 12:46             ` Laszlo Ersek
2019-06-26 13:16               ` Wang, Jian J

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=c6c028b2-2624-ab77-b6fe-ed080cd2cade@redhat.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