Here is an excerpt from the Debian hurd-i386 build log that @henrich kindly shared:

/bin/bash ../libtool  --tag=CC   --mode=compile gcc -DHAVE_CONFIG_H -I. -I/<<PKGBUILDDIR>>/./gutils -I.. -I../inc  "-I../inc" "-I/<<PKGBUILDDIR>>/./inc" "-I../lib" "-I/<<PKGBUILDDIR>>/./lib" -Wl,--no-undefined  -pthread -I/usr/include/glib-2.0 -I/usr/lib/i386-gnu/glib-2.0/include   -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/i386-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2        -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/i386-gnu/python2.7 -pthread  -Wdate-time -D_FORTIFY_SOURCE=2 -I.. -I/<<PKGBUILDDIR>>/.   -g -O2 -fdebug-prefix-map=/<<PKGBUILDDIR>>=. -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -c -o libgutils_la-fsys.lo `test -f 'fsys.c' || echo '/<<PKGBUILDDIR>>/./gutils/'`fsys.c
libtool: compile:  gcc -DHAVE_CONFIG_H -I. "-I/<<PKGBUILDDIR>>/./gutils" -I.. -I../inc -I../inc "-I/<<PKGBUILDDIR>>/./inc" -I../lib "-I/<<PKGBUILDDIR>>/./lib" -Wl,--no-undefined -pthread -I/usr/include/glib-2.0 -I/usr/lib/i386-gnu/glib-2.0/include -I/usr/include/pango-1.0 -I/usr/include/harfbuzz -I/usr/include/pango-1.0 -I/usr/include/cairo -I/usr/include/glib-2.0 -I/usr/lib/i386-gnu/glib-2.0/include -I/usr/include/pixman-1 -I/usr/include/freetype2 -I/usr/include/libpng16 -I/usr/include/freetype2 -I/usr/include/libxml2 -I/usr/include/python2.7 -I/usr/include/i386-gnu/python2.7 -pthread -Wdate-time -D_FORTIFY_SOURCE=2 -I.. "-I/<<PKGBUILDDIR>>/." -g -O2 "-fdebug-prefix-map=/<<PKGBUILDDIR>>=." -specs=/usr/share/dpkg/pie-compile.specs -fstack-protector-strong -Wformat -Werror=format-security -c "/<<PKGBUILDDIR>>/./gutils/fsys.c"  -fPIC -DPIC -o .libs/libgutils_la-fsys.o
/<<PKGBUILDDIR>>/./gutils/fsys.c:41:22: error: 'MAXPATHLEN' undeclared here (not in a function)
 static char dirname_[MAXPATHLEN+1];
                      ^~~~~~~~~~
/<<PKGBUILDDIR>>/./gutils/fsys.c: In function 'getLibexecDir_NonWindows':
/<<PKGBUILDDIR>>/./gutils/fsys.c:770:22: error: 'PATH_MAX' undeclared (first use in this function)
     static char path[PATH_MAX+4];
                      ^~~~~~~~
/<<PKGBUILDDIR>>/./gutils/fsys.c:770:22: note: each undeclared identifier is reported only once for each function it appears in
Makefile:1442: recipe for target 'libgutils_la-fsys.lo' failed
make[3]: *** [libgutils_la-fsys.lo] Error 1
make[3]: Leaving directory '/<<PKGBUILDDIR>>/build/nox/gutils'
Makefile:1575: recipe for target 'all-recursive' failed
make[2]: *** [all-recursive] Error 1
make[2]: Leaving directory '/<<PKGBUILDDIR>>/build/nox'
Makefile:1412: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/<<PKGBUILDDIR>>/build/nox'
/usr/share/cdbs/1/class/makefile.mk:77: recipe for target 'debian/stamp-makefile-build/nox' failed
make: *** [debian/stamp-makefile-build/nox] Error 2
dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2

In a nutshell: MAXPATHLEN and PATH_MAX are not defined on GNU Hurd, but they can easily be defined in a Fontforge C header file, e.g. this patch https://sources.debian.org/src/fontforge/1%3A20201107~dfsg-4/debian/patches/0004-hurd-PATH_MAX-and-MAXPATHLEN.patch/ which 2021-01-15 fontforge (1:20201107~dfsg-4).

Special thanks to @henrich for reporting the bug here in July 2017, and to @ucko for reporting fontforge: FTBFS on hurd-i386: PATH_MAX undeclared at https://bugs.debian.org/877795, and to @kilobyte for the discussion.

A pull request based on the aforementioned Debian patch will follow shortly.

build failure for GNU/Hurd #3119

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions