Your message dated Mon, 2 Jul 2018 21:44:23 +0200
with message-id <[email protected]>
and subject line Re: siridb-server: FTBFS on hurd-i386
has caused the Debian Bug report #885013,
regarding siridb-server: FTBFS on hurd-i386
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
885013: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=885013
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: siridb-server
Version: 2.0.25-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: [email protected]
Usertags: hurd-i386
The build of siridb-server for hurd-i386 (admittedly not a release
architecture) failed:
../src/xpath/xpath.c: In function 'xpath_get_exec_path':
../src/xpath/xpath.c:94:42: error: 'PATH_MAX' undeclared (first use in this
function); did you mean 'NAME_MAX'?
The Hurd famously has no static PATH_MAX. Best practice is to work
dynamically with what you encounter. However, if that's infeasible,
you can also look up _PC_PATH_MAX via pathconf or supply a fallback
constant (traditionally 4096).
Could you please take a look, bearing in mind that there's presumably
at least one more reference to PATH_MAX (in whatever calls
xpath_get_exec_path)?
Thanks!
--
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/[email protected]
--- End Message ---
--- Begin Message ---
Version: 2.0.27-1
On Fri, 2 Feb 2018 13:49:32 +0100 Paul Gevers <[email protected]> wrote:
> On Fri, 22 Dec 2017 16:11:47 -0500 "Aaron M. Ucko" <[email protected]> wrote:
> > Could you please take a look, bearing in mind that there's presumably
> > at least one more reference to PATH_MAX (in whatever calls
> > xpath_get_exec_path)?
>
> This specific issue was fixed upstream in version 2.0.26, but the
> package still FTBFS. That is due to bug 881882 in libuv1-dev, hence the
> block.
Bug 881882 was fixed last month. Version 2.0.27-1 was successfully build.
Paul
signature.asc
Description: OpenPGP digital signature
--- End Message ---
