bug-binutils
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the de


From: oset at superbox dot pl
Subject: [Bug binutils/32243] NAME_MAX does not exist on mingw-w64 without the define of _POSIX_ macro
Date: Wed, 09 Oct 2024 10:55:09 +0000

https://sourceware.org/bugzilla/show_bug.cgi?id=32243

oset <oset at superbox dot pl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |oset at superbox dot pl

--- Comment #4 from oset <oset at superbox dot pl> ---

NAME_MAX seem to 255 in VC.

VC9
~~~
$ grep -r -nH NAME_MAX *
limits.h:117:#define NAME_MAX            255
stdio.h:111:#define FILENAME_MAX    260
~~~

VC6
~~~
$ grep -r -nH NAME_MAX *
CRT/SRC/STDIO.H:216:#define FILENAME_MAX    260
(...)
Include/LIMITS.H:107:#define NAME_MAX            255
Include/STDIO.H:200:#define FILENAME_MAX    260
~~~

Same as in Linux:

~~~
$ grep -r -nH -w NAME_MAX *

linux/limits.h:11:#define NAME_MAX         255  /* # chars in a file name */
~~~

Same in MinGW
~~~
$ grep -r -nH -w NAME_MAX *

limits.h:108:#define NAME_MAX 255
~~~

I can't say for newer ones but it can be assumed that if it was N for X years
prior, it will be after. That is not something you change on a whim.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]