Skip to content

Conversation

@danbev
Copy link
Contributor

OpenSSL 3.0 has a number of header files that are generated, and
currently these headers are copied into the architecture specific
directories. This is done for each asm type, 'asm', 'asm_avx2', and
'no-asm' which has takes up quite a lot of disk space and also becomes
an issue with the headers.tar file which has increased due to this.

This commit adds copies the headers to a common directory for the
architecture, for example with linux-x86_64 there will be a directory
named deps/openssl/config/archs/linux-x86_64/common/include where the headers
will be copied (into subdirectories 'openssl' and 'crypto'. And in the
original locations a header file with the same name will be generated
which points (includes) the common header file.

Fixes: #42081

@nodejs-github-botnodejs-github-bot added dependencies Pull requests that update a dependency file. needs-ci PRs that need a full CI run. openssl Issues and PRs related to the OpenSSL dependency. labels Apr 5, 2022
@danbevdanbevforce-pushed the openssl-3.0.0-header-files branch from 47aaa16 to a0b44c6CompareApril 6, 2022 03:35
@nodejs-github-bot
Copy link
Collaborator

@danbev
Copy link
ContributorAuthor

With these changes the size of include/node/openssl/archs is:

$ du -hs node-v18.0.0/include/node/openssl/archs/37M node-v18.0.0/include/node/openssl/archs/

I'm not sure if this is acceptable or not but at least it is an improvement current size which is around 61M.

@danbevdanbevforce-pushed the openssl-3.0.0-header-files branch from a0b44c6 to b9babe6CompareApril 6, 2022 14:27
@nodejs-github-bot
Copy link
Collaborator

@mhdawson
Copy link
Member

I'm not sure if this is acceptable or not but at least it is an improvement current size which is around 61M.

Definitely a good improvement. I think we should compare to the pre-18.x size to judge whether this is a great first step or the complete fix.

@richardlau
Copy link
Member

I'm not sure if this is acceptable or not but at least it is an improvement current size which is around 61M.

Definitely a good improvement. I think we should compare to the pre-18.x size to judge whether this is a great first step or the complete fix.

It's a step in the right direction but still much bigger than when we were using OpenSSL 1.1.1. For comparison the equivalent directories in the headers package for Node.js 16.14.0 is 2.7M (#42081).

@danbev
Copy link
ContributorAuthor

For comparison the equivalent directories in the headers package for Node.js 16.14.0 is 2.7M (#42081).

I've added a comment to #42081 about the reason for the larger size in OpenSSL 3.x, compared to 1.1.1. While there might be more options to cut the size I don't think we will get it down to a size close to that of 1.1.1 as there are now more headers that are generated specifically for an architecture in 3.x than there were for 1.1.1. But I'll take another look and see if there is more that could be done.

@danbev
Copy link
ContributorAuthor

I've been able to find one set of headers that are not being used anymore, and another set for providers which could be shared per architecture like is done in this PR. I'll make these changes and see what the size of the headers.tar is after that.

@mhdawson
Copy link
Member

@danbev as an FYI some of the failures in the CI do look related to compiling openssl

@danbev
Copy link
ContributorAuthor

@danbev as an FYI some of the failures in the CI do look related to compiling openssl

Thanks, I'll complete the changes I've got and then run through CI again on Monday.

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@nodejs-github-bot
Copy link
Collaborator

@danbev
Copy link
ContributorAuthor

With the latest changes the sizes of the sub directories in archs in the produced headers tar file looks like this:

$ ls | xargs du -sch 1.5M aix64-gcc-as 1.5M aix-gcc 1.5M BSD-x86 1.5M BSD-x86_64 1.5M darwin64-arm64-cc 1.5M darwin64-x86_64-cc 1.5M darwin-i386-cc 1.5M linux32-s390x 1.5M linux64-mips64 1.1M linux64-riscv64 1.5M linux64-s390x 1.5M linux-aarch64 1.5M linux-armv4 1.5M linux-elf 1.5M linux-ppc 1.5M linux-ppc64 1.5M linux-ppc64le 1.5M linux-x86_64 1.5M solaris64-x86_64-gcc 1.5M solaris-x86-gcc 2.8M VC-WIN32 2.8M VC-WIN64A 936K VC-WIN64-ARM 35M total 

The windows variants are larger but they are also excluded from the headers handling that is part of this PR. We could look into them and see what can be done but if we assume that we can do something similar to what we have done to the others that would probably only get the total size down to something like 34M which I'm not really sure makes that much of a difference.

@richardlau
Copy link
Member

With the latest changes the sizes of the sub directories in archs in the produced headers tar file looks like this:

$ ls | xargs du -sch 1.5M aix64-gcc-as 1.5M aix-gcc 1.5M BSD-x86 1.5M BSD-x86_64 1.5M darwin64-arm64-cc 1.5M darwin64-x86_64-cc 1.5M darwin-i386-cc 1.5M linux32-s390x 1.5M linux64-mips64 1.1M linux64-riscv64 1.5M linux64-s390x 1.5M linux-aarch64 1.5M linux-armv4 1.5M linux-elf 1.5M linux-ppc 1.5M linux-ppc64 1.5M linux-ppc64le 1.5M linux-x86_64 1.5M solaris64-x86_64-gcc 1.5M solaris-x86-gcc 2.8M VC-WIN32 2.8M VC-WIN64A 936K VC-WIN64-ARM 35M total 

The windows variants are larger but they are also excluded from the headers handling that is part of this PR. We could look into them and see what can be done but if we assume that we can do something similar to what we have done to the others that would probably only get the total size down to something like 34M which I'm not really sure makes that much of a difference.

I'm wondering if we can get rid of some of these. e.g. aix-gcc, darwin-i386-cc, linux32-s390x, linux-ppc, linux-ppc64, solaris-x86-gcc.

@richardlau
Copy link
Member

I'm also not sure what linux-armv4 is.

@danbev
Copy link
ContributorAuthor

I'm wondering if we can get rid of some of these. e.g. aix-gcc, darwin-i386-cc, linux32-s390x, linux-ppc, linux-ppc64, solaris-x86-gcc.

I don't have the answer to that question, but I'd be all for removing them if they are no longer needed 👍

@mhdawson
Copy link
Member

@miladfarca can you check with Vascili on which of we need?

1.5M aix64-gcc-as
1.5M aix-gcc

@mhdawson
Copy link
Member

I think we could get rid of linux-ppc and linux-ppc64 as we only support linux-ppc64le as long as that is what is used for linux-ppc64 builds.

@miladfarca
Copy link
Contributor

miladfarca commented Apr 12, 2022

@miladfarca can you check with Vascili on which of we need?

1.5M aix64-gcc-as 1.5M aix-gcc

I've forwarded the link to Vasili to confirm.
Assuming -maix64 is used during build with gcc (like how its done on the V8 side) then 64 bit headers might need to be used i.e aix64-gcc-as.

@nodejs-github-bot
Copy link
Collaborator

danbev added a commit that referenced this pull request Apr 28, 2022
OpenSSL 3.0 has a number of header files that are generated, and currently these headers are copied into the architecture specific directories. This is done for each asm type, 'asm', 'asm_avx2', and 'no-asm' which has takes up quite a lot of disk space and also becomes an issue with the headers.tar file which has increased due to this. This commit adds copies the headers to a common directory for the architecture, for example with linux-x86_64 there will be a directory named deps/openssl/config/archs/linux-x86_64/common/include where the headers will be copied (into subdirectories 'openssl' and 'crypto'. And in the original locations a header file with the same name will be generated which points (includes) the common header file. PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danbev added a commit that referenced this pull request Apr 28, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danbev added a commit that referenced this pull request Apr 28, 2022
This arch was renamed to clarify that it used the aix assembler (as) and not the gnu assembler. It was removed from the Makefile and not being built but would still be picked up by make targets like the header-tar target. PR-URL: #42616Fixes: #42081 Refs: openssl/openssl@178fa72ed5 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danbev added a commit that referenced this pull request Apr 28, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danbev added a commit that referenced this pull request Apr 28, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
danbev added a commit that referenced this pull request Apr 28, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
@danbev
Copy link
ContributorAuthor

Landed in 33bc537, 4f1f14e, d8365ac, d68c4e9, 3f0b2a2, and 4ecfe3f

@danbevdanbev closed this Apr 28, 2022
targos pushed a commit that referenced this pull request May 2, 2022
OpenSSL 3.0 has a number of header files that are generated, and currently these headers are copied into the architecture specific directories. This is done for each asm type, 'asm', 'asm_avx2', and 'no-asm' which has takes up quite a lot of disk space and also becomes an issue with the headers.tar file which has increased due to this. This commit adds copies the headers to a common directory for the architecture, for example with linux-x86_64 there will be a directory named deps/openssl/config/archs/linux-x86_64/common/include where the headers will be copied (into subdirectories 'openssl' and 'crypto'. And in the original locations a header file with the same name will be generated which points (includes) the common header file. PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos pushed a commit that referenced this pull request May 2, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos pushed a commit that referenced this pull request May 2, 2022
This arch was renamed to clarify that it used the aix assembler (as) and not the gnu assembler. It was removed from the Makefile and not being built but would still be picked up by make targets like the header-tar target. PR-URL: #42616Fixes: #42081 Refs: openssl/openssl@178fa72ed5 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos pushed a commit that referenced this pull request May 2, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos pushed a commit that referenced this pull request May 2, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
targos pushed a commit that referenced this pull request May 2, 2022
PR-URL: #42616Fixes: #42081 Reviewed-By: James M Snell <[email protected]> Reviewed-By: Richard Lau <[email protected]>
@targostargos mentioned this pull request May 2, 2022
@yanovich
Copy link

commit 7fae2c9 breaks C++ addons which use any openssl header:

$ yarn build yarn run v1.22.18 $ node-gyp configure --silent && node-gyp build --silent make: Entering directory '/home/user/src/addon/build' CXX(target) Release/obj.target/addon/addon.o In file included from /home/s/.cache/node-gyp/18.1.0/include/node/openssl/opensslconf.h:9, from /home/s/.cache/node-gyp/18.1.0/include/node/openssl/macros.h:14, from /home/s/.cache/node-gyp/18.1.0/include/node/openssl/evp.h:14, from ../addon.cc:5: /home/s/.cache/node-gyp/18.1.0/include/node/openssl/./opensslconf_asm.h:97:11: fatal error: ./archs/linux-x86_64/asm/include/openssl/opensslconf.h: No such file or directory 97 | # include "./archs/linux-x86_64/asm/include/openssl/opensslconf.h" | ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ compilation terminated. make: *** [addon.target.mk:120: Release/obj.target/addon/addon.o] Error 1 $ head -n 5 addon.cc #include <stdlib.h> #include <string.h> #include <iostream> #include <openssl/evp.h> 

@juanarbol
Copy link
Member

This is a dep of #42356, so, this can not be landed in v16.x

Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependenciesPull requests that update a dependency file.needs-ciPRs that need a full CI run.opensslIssues and PRs related to the OpenSSL dependency.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Node.js OpenSSL headers much larger after OpenSSL 3 switch over

9 participants

@danbev@nodejs-github-bot@mhdawson@richardlau@miladfarca@V-for-Vasili@yanovich@juanarbol@jasnell