[Bug sanitizer/99476] New: 'PATH_MAX' was not declared in this scope

[Bug sanitizer/99476] New: 'PATH_MAX' was not declared in this scope

[unlvsur at live dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476

            Bug ID: 99476
           Summary: 'PATH_MAX' was not declared in this scope
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: sanitizer
          Assignee: unassigned at gcc dot gnu.org
          Reporter: unlvsur at live dot com
                CC: dodji at gcc dot gnu.org, dvyukov at gcc dot gnu.org,
                    jakub at gcc dot gnu.org, kcc at gcc dot gnu.org, marxin at gcc dot gnu.org
  Target Milestone: ---

Created attachment 50334
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=50334&action=edit
sanitizers do not find PATH_MAX and use linux headers

I try to cross compile gcc from windows to freebsd.
PATH_MAX does not exist.

[Bug sanitizer/99476] 'PATH_MAX' was not declared in this scope

[unlvsur at live dot com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476

--- Comment #1 from cqwrteur <unlvsur at live dot com> ---
../../../../../../../gcc/libsanitizer/asan/asan_linux.cpp: In function 'void
__asan::AsanCheckIncompatibleRT()':
../../../../../../../gcc/libsanitizer/asan/asan_linux.cpp:200:21: error:
'PATH_MAX' was not declared in this scope
  200 |       char filename[PATH_MAX];
      |                     ^~~~~~~~
../../../../../../../gcc/libsanitizer/asan/asan_linux.cpp:201:35: error:
'filename' was not declared in this scope; did you mean 'rename'?
  201 |       MemoryMappedSegment segment(filename, sizeof(filename));
      |                                   ^~~~~~~~
      |                                   rename

The bug is still in the source

[Bug sanitizer/99476] 'PATH_MAX' was not declared in this scope

[syq at debian dot org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476

YunQiang Su <syq at debian dot org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |syq at debian dot org

--- Comment #2 from YunQiang Su <syq at debian dot org> ---
Since commit
    59e4c98173a79fcaa2c33253261409f38856c384
You can add an configure option
    --includedir=/you/sysroot/include
to solve this problem.

/you/sysroot/include should contains a real workable limits.h.

The reason is due to that if gcc cannot find a limits.h,
it will use its ./gcc/glimits.h, which has no PATH_MAX defined.

[Bug sanitizer/99476] 'PATH_MAX' was not declared in this scope

[iii at linux dot ibm.com]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476

Ilya Leoshkevich <iii at linux dot ibm.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |iii at linux dot ibm.com

--- Comment #3 from Ilya Leoshkevich <iii at linux dot ibm.com> ---
I had a similar issue when compiling GCC targeting i686-linux on x86_64 debian,
and --includedir= helped, thanks! I had to do the following:

../configure --target=i686-linux-gnu --disable-bootstrap --prefix=/usr
--includedir=/usr/i686-linux-gnu/include

[Bug sanitizer/99476] 'PATH_MAX' was not declared in this scope

[pinskia at gcc dot gnu.org]

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=99476

Andrew Pinski <pinskia at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |INVALID

--- Comment #4 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
This has to do with the way you are doing the cross compiling. Either use a
sysroot (with --with-sysroot=DIR) or use includedir as directed below.