wbrawner/openssl
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Avoid test_errstr in a cross compiled configuration

Browse source 
There's too high a chance that the openssl app and perl get different
messages for some error numbers.

[extended tests]

Reviewed-by: Matt Caswell <matt@openssl.org>
(Merged from https://github.com/openssl/openssl/pull/7699)
This commit is contained in:
Richard Levitte 2018-11-23 18:53:32 +01:00
parent 3be389435f
commit 0777de15ff
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
test/recipes/02-test_errstr.t
View file

@ -9,6 +9,7 @@
use strict; use strict;
no strict 'refs'; # To be able to use strings as function refs no strict 'refs'; # To be able to use strings as function refs
use OpenSSL::Test; use OpenSSL::Test;
use OpenSSL::Test::Utils;
use Errno qw(:POSIX); use Errno qw(:POSIX);
use POSIX qw(strerror); use POSIX qw(strerror);
@ -22,6 +23,14 @@ use constant NUM_SYS_STR_REASONS => 127;
setup('test_errstr'); setup('test_errstr');
# In a cross compiled situation, there are chances that our
# application is linked against different C libraries than
# perl, and may thereby get different error messages for the
# same error.
# The safest is not to test under such circumstances.
plan skip_all => 'This is unsupported for cross compiled configurations'
if config('CROSS_COMPILE');
# These are POSIX error names, which Errno implements as functions # These are POSIX error names, which Errno implements as functions
# (this is documented) # (this is documented)
my @posix_errors = @{$Errno::EXPORT_TAGS{POSIX}}; my @posix_errors = @{$Errno::EXPORT_TAGS{POSIX}};