https://bugs.openldap.org/show_bug.cgi?id=9658

          Issue ID: 9658
           Summary: libldap fails to compile on Hurd: MAXPATHLEN
                    undeclared
           Product: OpenLDAP
           Version: 2.5.7
          Hardware: All
                OS: All
            Status: UNCONFIRMED
          Keywords: needs_review
          Severity: normal
          Priority: ---
         Component: build
          Assignee: [email protected]
          Reporter: [email protected]
  Target Milestone: ---

OpenLDAP 2.5 and later fails to compile on GNU/Hurd:

libtool: compile:  cc -g -O2 -I../../include -I../../include -DLDAP_LIBRARY -c
request.c  -fPIC -DPIC -o .libs/request.o
In file included from ldap-int.h:119,
                 from request.c:53:
request.c: In function 'ldap_dump_connection':
../../include/ldap_pvt.h:181:25: error: 'MAXPATHLEN' undeclared (first use in
this function)
  181 | #define LDAP_IPADDRLEN (MAXPATHLEN + sizeof("PATH="))
      |                         ^~~~~~~~~~
request.c:859:17: note: in expansion of macro 'LDAP_IPADDRLEN'
  859 |    char    from[LDAP_IPADDRLEN];
      |                 ^~~~~~~~~~~~~~
../../include/ldap_pvt.h:181:25: note: each undeclared identifier is reported
only once for each function it appears in
  181 | #define LDAP_IPADDRLEN (MAXPATHLEN + sizeof("PATH="))
      |                         ^~~~~~~~~~
request.c:859:17: note: in expansion of macro 'LDAP_IPADDRLEN'
  859 |    char    from[LDAP_IPADDRLEN];
      |                 ^~~~~~~~~~~~~~
Makefile:435: recipe for target 'request.lo' failed
make[2]: *** [request.lo] Error 1

This is not the same as ITS#9648. I have pulled latest master and the patch for
that one does not solve it.

GNU/Hurd actually does not have a MAXPATHLEN constant at all; paths are
expected to be dynamically allocated. See:
https://www.gnu.org/software/hurd/hurd/porting/guidelines.html#PATH_MAX_tt_MAX_PATH_tt_MAXPATHL

This is a low priority issue for me personally. I'm just filing it for
tracking. I'm hoping someone from the GNU/Hurd community might be able to work
on a patch.

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

Reply via email to