openssl/PROBLEMS - Issue 9254031: Upgrade chrome's OpenSSL to same version Android ships with.

Side by Side Diff: openssl/PROBLEMS

Issue 9254031: Upgrade chrome's OpenSSL to same version Android ships with. (Closed) Base URL: http://src.chromium.org/svn/trunk/deps/third_party/openssl/

Patch Set: '' Created 8 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

View unified diff | Download patch | Annotate | Revision Log

« openssl.gyp ('K') | « openssl/Netware/build.bat ('k') | openssl/README » ('j') | patches/x509_hash_name_algorithm_change.patch » ('J')

OLD	NEW
1 * System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X.	1 * System libcrypto.dylib and libssl.dylib are used by system ld on MacOS X.

2	2

3	3

4 NOTE: The problem described here only applies when OpenSSL isn't built	4 NOTE: The problem described here only applies when OpenSSL isn't built

5 with shared library support (i.e. without the "shared" configuration	5 with shared library support (i.e. without the "shared" configuration

6 option). If you build with shared library support, you will have no	6 option). If you build with shared library support, you will have no

7 problems as long as you set up DYLD_LIBRARY_PATH properly at all times.	7 problems as long as you set up DYLD_LIBRARY_PATH properly at all times.

8	8

9	9

10 This is really a misfeature in ld, which seems to look for .dylib libraries	10 This is really a misfeature in ld, which seems to look for .dylib libraries

(...skipping 18 matching lines...) Expand all Loading...
29	29

30 Another solution that many seem to recommend is to move the libraries	30 Another solution that many seem to recommend is to move the libraries

31 /usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different	31 /usr/lib/libcrypto.0.9.dylib, /usr/lib/libssl.0.9.dylib to a different

32 directory, build and install OpenSSL and anything that depends on your	32 directory, build and install OpenSSL and anything that depends on your

33 build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their	33 build, then move libcrypto.0.9.dylib and libssl.0.9.dylib back to their

34 original places. Note that the version numbers on those two libraries	34 original places. Note that the version numbers on those two libraries

35 may differ on your machine.	35 may differ on your machine.

36	36

37	37

38 As long as Apple doesn't fix the problem with ld, this problem building	38 As long as Apple doesn't fix the problem with ld, this problem building

39 OpenSSL will remain as is.	39 OpenSSL will remain as is. Well, the problem was addressed in 0.9.8f by

	40 passing -Wl,-search_paths_first, but it's unknown if the flag was

	41 supported from the initial MacOS X release.

40	42

41	43

42 * Parallell make leads to errors	44 * Parallell make leads to errors

43	45

44 While running tests, running a parallell make is a bad idea. Many test	46 While running tests, running a parallell make is a bad idea. Many test

45 scripts use the same name for output and input files, which means different	47 scripts use the same name for output and input files, which means different

46 will interfere with each other and lead to test failure.	48 will interfere with each other and lead to test failure.

47	49

48 The solution is simple for now: don't run parallell make when testing.	50 The solution is simple for now: don't run parallell make when testing.

49	51

(...skipping 138 matching lines...) Expand 10 before \| Expand all \| Expand 10 after Loading...
188 either as or ld, and was observed on FreeBSD and Linux. There are two	190 either as or ld, and was observed on FreeBSD and Linux. There are two

189 options. First is naturally to upgrade binutils, the second one - to	191 options. First is naturally to upgrade binutils, the second one - to

190 reconfigure with additional no-sse2 [or 386] option passed to ./config.	192 reconfigure with additional no-sse2 [or 386] option passed to ./config.

191	193

192 * If configured with ./config no-dso, toolkit still gets linked with -ldl,	194 * If configured with ./config no-dso, toolkit still gets linked with -ldl,

193 which most notably poses a problem when linking with dietlibc.	195 which most notably poses a problem when linking with dietlibc.

194	196

195 We don't have framework to associate -ldl with no-dso, therefore the only	197 We don't have framework to associate -ldl with no-dso, therefore the only

196 way is to edit Makefile right after ./config no-dso and remove -ldl from	198 way is to edit Makefile right after ./config no-dso and remove -ldl from

197 EX_LIBS line.	199 EX_LIBS line.

OLD	NEW