fix escript archive symlinked across drives

real_path method used while prim loading archive files was not taking into account
the fact that windows directory symlinks can be across different drives
(eg. c:\tmp\test is a symlink to j:\tmp\test). when performing a path split the drive
precedes the symlink, but that has be rewritten also since it's different. This issue
never arises in Unix since obviously there are no drives
Fix a typo in clean section of otp_mibs makefile

There is no such variable $(TARGETS_FILES) (with S)
Cleanup behaviour modules in ssh

Behaviour modules were not cleanuped.
Cleanup behaviour modules in ssl

Behaviour modules were not cleanuped.
Cleanup parse_transform modules in eunit

Parse_transform modules were not cleanuped.
Fix filelib:wildcard/2 when 'Cwd' ends with a dot

In such case, filelib:wildcard/2 returned truncated results:

  1> file:set_cwd("/usr/lib/erlang/lib").
  ok
  2> filelib:wildcard("stdlib-*/ebin/*.app", filename:absname(".")).
  ["dlib-2.1/ebin/stdlib.app"]
Use compile options when dialyzing beam files

Fetch the compile options from beam files, and use them when creating
core from the abstract code. Previously the options were ignored.

Test by Henrik Nordh
Tweak comments
Add diameter_dbg:sizes/0

To return sizes of named ets tables.
Add (process) info tuple to diameter:service_info/2

To show process_info of interest. This is not yet documented since it
may well change.
Add info item for diameter:service_info/2

To extract only process info from connections info, which can be useful
to reduce the amount of information returned.

Choose 'info' for the item since process_info is more than one word: all
others are one. Don't choose memory since it's too specific: might want
to use it for more.
Fix some spelling misstakes
Allow Name/Arity syntax in maps inside attributes

Currently Name/Arity syntax is supported in list and tuple terms. This change makes it possible to use this syntax in map terms for consistency and convenience.

Example:
-custom(#{test1 => init/2, test2 => [val/1, val/2]}).
Fix counting of outgoing requests

Commit df19c272 broke this in avoiding counting on arbitrary keys.
It didn't break it sufficiently for the only counters usage in the test
suites to fail however: watchdog counters worked as intended, but no
others, not even CER and DPR. More testcases are needed.

This commit does change/fix the previous semantics somewhat:

- Retransmissions are no longer counted. This previously made it
  impossible to distinguish between these and unanswered requests, since
  both counted as an outgoing request. There should probably be a
  retransmission counter but it should be distinct from the sent request
  counter.

- The counting is always on the node from which diameter:call/4 is
  invoked, not the node on which the transport resides, as was previously
  the case. (Although they're typically one and the same.)

Note that none of these semantics are documented as yet, so we're not
changing a documented interface.
Count request retransmissions

As mentioned in the parent commit. The {Id, send, retransmission}
key is of the same form as the {Id, send|recv, error} key used for
encode/decode errors.
Count relayed messages on {relay, Rbit}

Instead of grouping them with 'unknown'. These messages were keyed on
{ApplicationId, CommandCode, Rbit} prior to commit df19c272, but
distinguishing between the relay application and others is probably more
useful.

The only reason for not including the R-bit in the unknown key is that
the key is also used elsewhere, and relay is an expected case while
unknown isn't.
Map binary process info to a reference/byte count

That is, instead of including the list in a diameter:service_info/2 info
tuple, only include the number of references and the number of bytes
referenced. The list itself can be quite large and typically isn't that
interesting, at least not to a diameter user.
fix indentation, add comment describing windows symlink creation assumption
Fix HiPE debug lock checking on OS X 64bit

Position-independent code is mandatory on OS X. We use r11 as an intermediate
register to fill BIF_P->hipe.bif_callee. This fixes the following error when
doing `make debug FLAVOR=smp`:

clang -cc1as: fatal error: error in backend: 32-bit absolute addressing is not supported in 64-bit mode
Rewrite manager net_if for IPv4+IPv6