diff options
| author | Richard Levitte <levitte@openssl.org> | 2017-03-15 02:52:20 +0100 |
|---|---|---|
| committer | Richard Levitte <levitte@openssl.org> | 2017-03-15 03:09:57 +0100 |
| commit | 1ae4c07e50a4988c7e2263ad669dc75fe2d494cb (patch) | |
| tree | f8ce78bf369fe894c6f67796c19775b235e7d56c /util/unlocal_shlib.com.in | |
| parent | Add Python Cryptography.io external test suite (diff) | |
| download | openssl-1ae4c07e50a4988c7e2263ad669dc75fe2d494cb.tar.xz openssl-1ae4c07e50a4988c7e2263ad669dc75fe2d494cb.zip | |
VMS: don't use /DSF, turn off CALL_DEBUG instead
It turns out that /DSF didn't do any good for our purposes. Instead,
remove the CALL_DEBUG flag from any image we link. This ensures that
we can have debugging information in the image files, but don't
automatically end up in a debugging session upon image activation.
Unfortunately, this means the CALL_DEBUG must be turned on when there
is a need to run with the debugger activated, and to turn it off when
done. This has been documented in NOTES.VMS.
Reviewed-by: Rich Salz <rsalz@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/2957)
Diffstat (limited to 'util/unlocal_shlib.com.in')
| -rw-r--r-- | util/unlocal_shlib.com.in | 7 |
1 files changed, 3 insertions, 4 deletions
diff --git a/util/unlocal_shlib.com.in b/util/unlocal_shlib.com.in index 67120c6e78..dd4fd2a9dd 100644 --- a/util/unlocal_shlib.com.in +++ b/util/unlocal_shlib.com.in @@ -2,10 +2,9 @@ ${- use File::Spec::Functions qw(rel2abs); my $bldtop = rel2abs($config{builddir}); - our %names = ( ( map { $_ => $bldtop.$_.".EXE" } - map { $unified_info{sharednames}->{$_} || () } - @{$unified_info{libraries}} ), - 'DBG$IMAGE_DSF_PATH' => $bldtop ); + our %names = ( map { $_ => $bldtop.$_.".EXE" } + map { $unified_info{sharednames}->{$_} || () } + @{$unified_info{libraries}} ); "" -} $ ! Remove the local environment created by local_shlib.com $ |