This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libfortran/47375] New: getlog causes warnings with static linking
- From: "Joost.VandeVondele at pci dot uzh.ch" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Jan 2011 11:27:58 +0000
- Subject: [Bug libfortran/47375] New: getlog causes warnings with static linking
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47375
Summary: getlog causes warnings with static linking
Product: gcc
Version: 4.6.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: libfortran
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: Joost.VandeVondele@pci.uzh.ch
The following testcase causes the following warning when linking. If the static
binary is afterwards used on 'the right system' it will also crash. It would be
nice if the getlog implementation avoids this problem, some HPC systems only
allow for static linking.
> cat test.f90
character(LEN=80) :: name
CALL getlog(name)
END
> gfortran -static test.f90
/usr/lib64/gcc/x86_64-suse-linux/4.5/libgfortran.a(getlog.o): In function
`_gfortran_getlog':
/usr/src/packages/BUILD/gcc-4.5.0-20100604/obj-x86_64-suse-linux/x86_64-suse-linux/libgfortran/../../../libgfortran/intrinsics/getlog.c:80:
warning: Using 'getpwuid' in statically linked applications requires at runtime
the shared libraries from the glibc version used for linking