Patch release : otp_src_R7B-1 From snapshot : 20001128 The patch handling was changed so now there are new releases and one patch to get you from the previous release to the current release. In more detail: 1. We release fully tested source base releases. This is R7B-0, R8A-0, i.e. those ending in "-0". 2. We release selected source snapshots. This is snapshots that contains important changes and that passed the testing. These snapshots will be named R7B-1, R7B-2, ...... 3. We will release combined patches, i.e. one large patch that patch from R7B-0 to R7B-1, a second one from R7B-1 to R7B-2 etc. Note that the result after patching will not be exactly the same as the snapshot. Some precompiled BEAM files in the bootstrap part may differ. 4. When a move from one source release to the next require changes in the bootstrap compiler, then there will be no patch to upgrade. This forces a complete source release download with the correct binary BEAM files. 5. Binary releases for Linux, FreeBSD and Windows will be built from the complete source snapshots, i.e. not from a base source release with applied patches. To patch you need a patch program that can handle the "unified" diff format. You apply the patch with % cd otp_src_R7B-0 % zcat ../otp_src_R7B-0to1.patch.gz | patch -p1 The changes from the previous patch level are VxWorks -------- Various changes made after the Unix release. snmp OTP-3704 It is now possible to register/unregister for notification of changes stored (permanently, i.e. on disk) in snmp_local_db. OTP-3725 Added direct access (read) functions to the symbolic store for faster access (accessible through the snmp module). erts OTP-3715 -nohup must work in Windows; erlsrv depends on it. -------- Changes for VxWorks and Windows done after the Unix release. kernel OTP-3714 When R6 nodes and unpatched R7 nodes are in the same network, global:register_name hangs. This is fixed with a patch to R7. Patched R7 nodes can communicate with unpatched R7 nodes OTP-3716 disk_log handles huge terms better when reading log files using chunk/2. Bugs in chunk/2 and chunk_step/3 as well as in wrap_log_reader have been fixed. OTP-3718 Kernel example uds_dist should not be read-only OTP-3763 inet_res:nslookup/4 has been made backwards compatible. OTP-3769 When making rpc:call to a function that in its turn spawn_linked some child process, the rpc server killed the child process when the called function returned. This is now corrected. configure OTP-3717 Corrected the configuration script for building with SSL. You can give the configure script the options --with-ssl use SSL (default) --with-ssl=PATH specify location of openSSL/ssleay include and lib --without-ssl don't use SSL Created from a patch contributed by Geoff Wong. -------- Updated the README file how to install the documentation. -------- Terminate configure if 'ar' command is not found. OTP-3785 For newer versions of gcc the value of GCCLIB_PATH is set incorrectly. In fact, it is not needed and now removed. erl_interface OTP-3719 The configure script did not define HAVE_STRDUP, hence the file erl_connect.c could not compile. The file erl_connect.c is now changed to not trust HAVE_STRDUP to be defined in config.h. Thanks to Mikael Pettersson and Geoff Wong. OTP-3772 Changed back the return values from erl_send() and erl_reg_send() to 1 (as they used to be). compiler OTP-3748 The compiler would sometimes reorder bit syntax clauses causing them to be execute in the wrong order. This has been corrected. jinterface OTP-3721 An error in the constructor for OtpNode has been fixed. mnesia OTP-3584 transform_table now supports indexes, but the dirty_index_* operations may exit when the index is rebuilt. The memory usage has been improved for set and ordered_set tables. OTP-3762 Same as OTP-3584 above. OTP-3761 New iteration functions has been added i.e. foldl/3 foldr/3 foldl/4 foldr/4, together with dirty_last/1 and dirty_prev/2 for ordered_set tables. sasl OTP-3767 A printout has been added in release_handler when install_release fails. stdlib OTP-3766 When doing a rpc:call to a remote node calling a function whos process gets killed by another process e.g. due to a link, the process calling rpc:call hanged. This bug is now fixed.