Searched refs:platform (Results 26 – 50 of 83) sorted by relevance
1234
/openssl/doc/internal/man3/ |
H A D | ossl_ends_with_dirsep.pod | 19 separator in a platform agnostic way. 22 a platform agnostic way.
|
/openssl/include/crypto/ |
H A D | dso_conf.h.in | 17 # of view. However, the "method"s may return zero unless that platform 32 # define DSO_EXTENSION "{- platform->dsoext() -}"
|
/openssl/ |
H A D | NOTES-NONSTOP.md | 10 * The TNS/X platform supports hardware randomization. 14 * The TNS/E platform does not support hardware randomization, so 22 prerequisite needed to build OpenSSL 3.0 on this platform. You should also 31 the TNS/X (L-Series) platform: 41 The TNS/E platform is build using the same set of builds specifying `nse` 83 The current OpenSSL default memory model uses the default platform address 143 **Note:** None of these builds have been tested by the platform maintainer and 171 If you require a VPROC entry for platform version identification, use the
|
H A D | NOTES-ANDROID.md | 24 will be "calculated" automatically based on chosen platform. However, 36 an older platform pass the argument `-D__ANDROID_API__=N` to `Configure`, 37 with `N` being the numerical value of the target platform version. For example, 69 for single specific platform including Android API level, and assign its
|
H A D | README.md | 105 platforms, the installation instructions are amended by a platform specific 111 * [Notes for the DOS platform with DJGPP](NOTES-DJGPP.md) 112 * [Notes for the OpenVMS platform](NOTES-VMS.md)
|
H A D | appveyor.yml | 4 platform:
|
H A D | NOTES-WINDOWS.md | 45 via <https://platform.activestate.com/ActiveState> and then download it. 80 - `perl Configure` to let Configure figure out the platform 125 - You should define the platform type to `uwp` and the target arch via
|
H A D | INSTALL.md | 59 For additional platform specific requirements, solutions to specific 65 * [Notes for the DOS platform with DJGPP](NOTES-DJGPP.md) 66 * [Notes for the OpenVMS platform](NOTES-VMS.md) 498 This option will be forced on a platform that does not support AFALG. 605 This option will be forced if on a platform that does not support CAPI. 1061 by a platform specific character (':' or 1152 In previous version, the `config` script determined the platform type and 1180 Please use the appropriate form for your platform. 1265 your privileges temporarily if your platform allows it). 1402 Use a different build file name than the platform default [all …]
|
/openssl/Configurations/ |
H A D | platform.pm | 1 package platform; package
|
/openssl/doc/man3/ |
H A D | BIO_s_socket.pod | 18 round the platform's socket routines. 35 Windows is one such platform. Any code mixing the two will not work on
|
H A D | CRYPTO_THREAD_run_once.pod | 77 operations are supported on the specific platform. Because of this, if a 87 specific platform. Because of this, if a variable is modified by 96 platform. Because of this, if a variable is modified by CRYPTO_atomic_or() or
|
H A D | BIO_ADDRINFO.pod | 40 types provided on your platform. 94 The BIO_lookup_ex() implementation uses the platform provided getaddrinfo()
|
H A D | BN_zero.pod | 23 for the most efficient implementation on the local platform.
|
H A D | OPENSSL_instrument_bus.pod | 39 not available on current platform. For reference, on x86 'flush cache
|
H A D | ASYNC_start_job.pod | 155 can be used to detect whether the current platform is async capable or not. 157 Custom memory allocation functions are supported for the POSIX platform. 182 ASYNC_is_capable() returns 1 if the current platform is async capable or 0 186 the current platform and no allocations have already occurred or 0 otherwise.
|
/openssl/test/recipes/ |
H A D | 03-test_fipsinstall.t | 23 use platform; 29 my $infile = bldtop_file('providers', platform->dso('fips'));
|
H A D | 04-test_encoder_decoder.t | 21 use platform;
|
H A D | 20-test_cli_fips.t | 24 use platform; 31 my $fipsmodule = bldtop_file('providers', platform->dso('fips'));
|
/openssl/engines/ |
H A D | e_afalg.txt | 10 AFALG_R_FAILED_TO_GET_PLATFORM_INFO:111:failed to get platform info
|
/openssl/Configurations/platform/ |
H A D | BASE.pm | 1 package platform::BASE;
|
/openssl/util/ |
H A D | shlib_wrap.sh.in | 6 use platform;
|
/openssl/test/ |
H A D | README.md | 12 (or disable your privileges temporarily if your platform allows it). 137 Depending on the platform characteristics, running more than one test job in 162 platform used.
|
/openssl/VMS/ |
H A D | openssl_shutdown.com.in | 29 $ sv := {- platform->shlib_version_as_filename(); -}
|
/openssl/doc/man7/ |
H A D | openssl-threads.pod | 15 Multi-platform applications can also use this API. 74 while L<CRYPTO_malloc(3)> assumes the underlying platform allocation
|
/openssl/doc/internal/man7/ |
H A D | build.info.pod | 49 This is about choice of platform (combination of hardware, operating 94 F<build.info> files are platform agnostic. This means that there is 111 These platform specific decorations are not the concern of 113 transforming these platform agnostic names to their platform specific 597 This is any platform specific file that describes the complete build, 598 with platform specific commands. On Unix, this is typically
|
Completed in 53 milliseconds
1234