[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-25 Thread fxcoudert at gcc dot gnu dot org
--- Comment #21 from fxcoudert at gcc dot gnu dot org 2007-04-25 08:39 --- Subject: Bug 31299 Author: fxcoudert Date: Wed Apr 25 08:38:59 2007 New Revision: 124144 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124144 Log: PR libfortran/31299 * intrinsic.texi (G

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-25 Thread fxcoudert at gcc dot gnu dot org
--- Comment #20 from fxcoudert at gcc dot gnu dot org 2007-04-25 08:37 --- Fixed on mainline. -- fxcoudert at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-25 Thread fxcoudert at gcc dot gnu dot org
--- Comment #19 from fxcoudert at gcc dot gnu dot org 2007-04-25 08:36 --- Subject: Bug 31299 Author: fxcoudert Date: Wed Apr 25 08:36:20 2007 New Revision: 124143 URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=124143 Log: PR libfortran/31299 * intrinsics/getlog

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-18 Thread dfranke at gcc dot gnu dot org
--- Comment #18 from dfranke at gcc dot gnu dot org 2007-04-18 19:39 --- > It happens when you compile and link statically a Fortran code > that uses GETLOG(). Confirmed. But if and only if it uses GETLOG(). Thus, it's not too bad. From comment #13, I assumed that the warning is issue

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-18 Thread fxcoudert at gcc dot gnu dot org
--- Comment #17 from fxcoudert at gcc dot gnu dot org 2007-04-18 19:21 --- (In reply to comment #16) > nor while compiling/linking > a binary (a hello-world in this case, glibc-2.5) It happens when you compile and link statically a Fortran code that uses GETLOG(). I've ended up convin

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-18 Thread dfranke at gcc dot gnu dot org
--- Comment #16 from dfranke at gcc dot gnu dot org 2007-04-18 19:15 --- FX, which version of glibc do you have installed? I applied your patch to an otherwise unpatched tree and do not get any warnings, neither at compile time of libgfortran(*) nor while compiling/linking a binary (a

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-18 Thread fxcoudert at gcc dot gnu dot org
--- Comment #15 from fxcoudert at gcc dot gnu dot org 2007-04-18 17:57 --- (In reply to comment #14) > As FX kindly provided a patch in comment #13, are there any plans to pick it > up > and commit it? As I said, I'm not sure it's the best thing to do, because it gives a warning for s

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-04-18 Thread dfranke at gcc dot gnu dot org
--- Comment #14 from dfranke at gcc dot gnu dot org 2007-04-18 17:26 --- As FX kindly provided a patch in comment #13, are there any plans to pick it up and commit it? -- dfranke at gcc dot gnu dot org changed: What|Removed |Added

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-03-26 Thread fxcoudert at gcc dot gnu dot org
--- Comment #13 from fxcoudert at gcc dot gnu dot org 2007-03-26 10:33 --- Below is a patch to use geteuid() and getpwuid(). One minor thing is that linking with glibc now warns at compile time for static linking: ../../../../trunk/libgfortran/intrinsics/getlog.c:97: warning: Using 'ge

[Bug libfortran/31299] Use getpwuid(geteuid()) instead of getlogin() for GETLOG()

2007-03-23 Thread fxcoudert at gcc dot gnu dot org
--- Comment #12 from fxcoudert at gcc dot gnu dot org 2007-03-23 21:28 --- Confirming this as a low-priority enhancement. After all, even though we have historical reasons to implement GETLOG using getlogin(), if the information returned by another scheme is more relevant *in all cases*