Bug#888392: mariadb-connector-c: FTBFS on non-Linux: version script unused
Source: mariadb-connector-c Version: 2.3.3-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-hurd@lists.debian.org Usertags: hurd Builds of mariadb-connector-c for (non-release) non-Linux architectures -- hurd-i386 so far [1] -- have been failing because the .symbols file expects versioned symbols, whereas the actual symbols remain unversioned. The issue appears to be that line 398 of [2] is specifically conditional on Linux. (Per [3], the less narrowly conditional reference to mariadbclient.def on line 378 is evidently pointless.) Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=mariadb-connector-c&arch=hurd-i386&ver=3.0.3-1&stamp=1516561406&raw=0 [2] https://salsa.debian.org/mariadb-team/mariadb-connector-c/blob/master/libmariadb/CMakeLists.txt [3] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888228#12 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#888395: charliecloud: FTBFS on non-Linux
Source: charliecloud Version: 0.2.3~git20171120.1a5609e-2 Severity: important Justification: fails to build from source User: debian-hurd@lists.debian.org Usertags: hurd Hi, Lucas. The build of charliecloud for hurd-i386 (admittedly not a release architecture) failed: ch-run.c:20:10: fatal error: sys/mount.h: No such file or directory The Hurd is unusual in not having traditional mount and umount system calls *at all* (instead letting administrators associate mount points with "translators" [1]). However, this program also contains plenty of outright Linuxisms, so I would expect kFreeBSD builds to fail too. As such, please formally declare this package's architecture to be linux-any so that non-Linux autobuilders don't bother trying to cover it. Thanks! [1] https://www.gnu.org/software/hurd/hurd/translator.html -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
Bug#888398: mblaze: FTBFS on hurd-i386: PATH_MAX undeclared
Source: mblaze Version: 0.2-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-hurd@lists.debian.org Usertags: hurd The build of mblaze for hurd-i386 (admittedly not a release architecture) failed with multiple errors of the form seq.c:21:19: error: 'PATH_MAX' undeclared (first use in this function); did you mean 'INT8_MAX'? as detailed in [1]. The Hurd notoriously has no static PATH_MAX. Best practice is dynamically accommodating whatever you actually encounter, since fixed-size buffers generally run the risk of either wasting memory or yielding truncation (or, worse, buffer overflows). However, if that's infeasible, you can also look up _PC_PATH_MAX via pathconf or even supply a fallback constant (traditionally 4096). Could you please take a look? Thanks! [1] https://buildd.debian.org/status/fetch.php?pkg=mblaze&arch=hurd-i386&ver=0.2-1&stamp=1516620274&raw=0 -- Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org) http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu
