Please do not use MAXPATHLEN, it is a arbitrary limit, and is not defined on GNU. Currently this makes building gcc-4.0 fail on GNU since gcc/ada/adaint.c assumes that MAXPATHLEN is defined. Please do not use these kind of limits in GNU programs. Not having MAXPATHLEN is perfectly compliant with POSIX, same goes for MAXHOSTNAMELEN, PATH_MAX etc.
Confirmed, it is more than adaint.c.
Subject: Bug 23187 CVSROOT: /cvs/gcc Module name: gcc Changes by: charlet@gcc.gnu.org 2005-08-29 13:07:07 Modified files: gcc/ada : adaint.c Log message: PR ada/23187 (GNAT_MAXPATH_LEN): Use default value if MAXPATHLEN is undefined. Patches: http://gcc.gnu.org/cgi-bin/cvsweb.cgi/gcc/gcc/ada/adaint.c.diff?cvsroot=gcc&r1=1.51&r2=1.52
Should not cause compilation error any more. Arno
Subject: Re: MAXPATHLEN usage in gcc/ada/*.c This patch is a kludge, GNU does not have any limit what-so-ever on the length of a filename. And it is a horrible kludge, since it is common to have filenames longer than 256 chars.
Subject: Re: MAXPATHLEN usage in gcc/ada/*.c ------- Additional Comments From charlet at gcc dot gnu dot org 2005-08-29 13:14 ------- Should not cause compilation error any more. The fix is wrong, GNU doesn't have any limit on the length of filenames. Defining a atribitary limit is not a fix.
Reopened bug awaiting a proper fix.
Subject: Re: MAXPATHLEN usage in gcc/ada/*.c > Reopened bug awaiting a proper fix. Feel free to submit one, since you have access to a GNU system. Arno
You also have access to a GNU system, GNU/Linux. It is easily testable there. Could you revert the fix? It is better that fails loudly than having a arbitrary limit. I'll see about submiting a proper patch.
Alfred, any news?
Lowering priority, 3 years without feedback despite a new request 7 months ago.
No feedback 3 years.