This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug fortran/23065] MAXPATHLEN usage in fortran/{scanner,module}.c
- From: "ams at gnu dot org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 1 Aug 2005 17:48:09 -0000
- Subject: [Bug fortran/23065] MAXPATHLEN usage in fortran/{scanner,module}.c
- References: <20050725203426.23065.schwinge-bugzilla-gcc.gnu.org@nic-nac-project.de>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Additional Comments From ams at gnu dot org 2005-08-01 17:48 -------
Subject: Re: MAXPATHLEN usage in fortran/{scanner,module}.c
So, does GNU define _POSIX_PATH_MAX?
No.
Does GNU support pathconf()?
Yes.
I read the other thread where it is suggested that a non-portable
GNU extension should be used. The gfortran source is fairly clean
from such kludges, and I would oppose the introduction of one.
In this case using getcwd(NULL, 0) (and it is easy to make this
portable), isn't neeed. But there is nothing "kludgy" about GNU
programs using GNU extentions.
In either case, I have a patch in the brew that should fix all
MAXPATHLEN/PATH_MAX issues in the whole GCC tree, which I will post as
soon as I have tested it (should be in few days).
Happy hacking.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23065