* hb/stdlib/gen_call_improvement/OTP-9212: Remove the undocumented function global:safe_whereis_name/1 Remove all use of global:safe_whereis_name/1 Fix a minor race in gen_fsm
* ia/ssl/test-maintenance: Removed compiler warnings Work around bug in openss-1.0.0e Use ERL_FLAGS in plain_verify_options test Adjustment to work with hipe Avoid openssl processes surviving after test case has finished Add better error message Skip ssl_dist_SUITE if cover run, as the test server node can not communicate with the ssl nodes with erlang distribution Fine tuning of test suites
If the server process is always closed first shutdown of the openssl process will be gracious
…municate with the ssl nodes with erlang distribution
E.g OpenBSD's (5.0) patched named does not allow itself to be started without privilige separation, which is only allowed for the superuser so test suites can not use that named. Fix the shell script that starts named to detect early exit from named and inform the Erlang code test suite what happened.
Common file target.mk now passes the TARGET value through config.sub for canonification. Toplevel Makefile now calls target.mk so it handles TARGET like all sub-makefiles. Build script otp_build no longer creates a target specific directory that a long time ago was used for target specific configure cache file.
* ia/public_key/ssl/crypto/PKCS-8/OTP-9312: Add clause for expected input to pubkey:pseudo_random_function/2 when ASN-1 compiler is fixed. Clean up of public_key code adding specs and documentation Added PKCS-8 support in ssl Additions to crypto and public_key needed for full PKCS-8 support Add PKCS-8 support to public_key
If parallel make is used, several instance of 'erlc' is likely to be invoked at once. Therefore, the default binding of schedulers to CPU cores will do no good. (With this change, the build of Erlang/OTP with six threads finished in about 7 minutes; without in about 11 minutes.)
Calls to global:whereis_name/1 have been substituted for calls to global:safe_whereis_name/1 since the latter is not safe at all. The reason for not doing this earlier is that setting a global lock masked out a bug concerning the restart of supervised children. The bug has now been fixed by a modification of global:whereis_name/1. (Thanks to Ulf Wiger for code contribution.)