mirror of
https://github.com/openssl/openssl.git
synced 2024-11-27 05:21:51 +08:00
fcd9c8c014
On VMS, the C compiler can work with 32-bit and 64-bit pointers, and the command line determines what the initial pointer size shall be. However, there is some functionality that only works with 32-bit pointers. In this case, it's gethostbyname(), getservbyname() and accompanying structures, so we need to make sure that we define our own pointers as 32-bit ones. Furthermore, there seems to be a bug in VMS C netdb.h, where struct addrinfo is always defined with 32-bit pointers no matter what, but the functions handling it are adapted to the initial pointer size. This leads to pointer size warnings when compiling with /POINTER_SIZE=64. The workaround is to force struct addrinfo to be the 64-bit variant if the initial pointer size is 64. Reviewed-by: Andy Polyakov <appro@openssl.org> |
||
|---|---|---|
| .. | ||
| b_addr.c | ||
| b_dump.c | ||
| b_print.c | ||
| b_sock2.c | ||
| b_sock.c | ||
| bf_buff.c | ||
| bf_lbuf.c | ||
| bf_nbio.c | ||
| bf_null.c | ||
| bio_cb.c | ||
| bio_err.c | ||
| bio_lcl.h | ||
| bio_lib.c | ||
| bio_meth.c | ||
| bss_acpt.c | ||
| bss_bio.c | ||
| bss_conn.c | ||
| bss_dgram.c | ||
| bss_fd.c | ||
| bss_file.c | ||
| bss_log.c | ||
| bss_mem.c | ||
| bss_null.c | ||
| bss_sock.c | ||
| build.info | ||
| Makefile.in | ||