Janne Blomqvist 563a18bc20 Don't assume __secure_getenv is available ... Glibc 2.17 made __secure_getenv an officially supported function, and renamed it secure_getenv. The libgfortran configure has checked for both of these, per https://sourceware.org/glibc/wiki/Tips_and_Tricks/secure_getenv. Unfortunately, while the dynamical library (libc.so) retains the __secure_getenv symbol for backwards compatibility, the static library (libc.a) does not. This means that a libgfortran.a compiled against an older glibc will not work if one tries to link against a newer libc.a. This creates problems for providing gfortran binary distributions that work on as many target systems as possible. Thus, retain the support for __secure_getenv but call it only via a weak reference. Backported from trunk. 2017-05-19 Janne Blomqvist <jb@gcc.gnu.org> * libgfortran.h: HAVE_SECURE_GETENV: Don't check HAVE___SECURE_GETENV. * environ/runtime.c (secure_getenv): Use __secure_getenv via a weak reference. From-SVN: r248273		2017-05-19 16:25:21 +03:00
..
backtrace.c
bounds.c
compile_options.c
convert_char.c
environ.c
error.c
fpu.c
in_pack_generic.c
in_unpack_generic.c
main.c
memory.c
minimal.c
pause.c
select_inc.c
select.c
stop.c
string.c