Your message dated Sat, 27 Jan 2018 00:28:51 +0800
with message-id
<CAAXyoMOg0MTOiBX8f1w2_U0Mf9fRnw7u8MOr72NPL+Yy_-iX=w...@mail.gmail.com>
and subject line Re: Bug#888067: tl-cpputils: FTBFS on hurd-i386: PATH_MAX not
declared
has caused the Debian Bug report #888067,
regarding tl-cpputils: FTBFS on hurd-i386: PATH_MAX not declared
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.)
--
888067: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888067
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: tl-cpputils
Version: 1.0-1
Severity: important
Tags: upstream
Justification: fails to build from source
User: [email protected]
Usertags: hurd-i386
The build of tl-cpputils for hurd-i386 (admittedly not a release
architecture) failed:
/<<PKGBUILDDIR>>/src/tl-cpputils/filesystem_path.cpp:231:21: error:
'PATH_MAX' was not declared in this scope
The Hurd infamously has no static PATH_MAX. There are various ways to
deal with this limitation, depending on context. In this case, I'd
recommend simply letting realpath allocate a buffer itself:
char *absolutePath = realpath(_path.c_str(), nullptr);
if (absolutePath == nullptr)
return {};
_absolutePath = std::string(absolutePath);
free(absolutePath);
Could you please take a look?
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 ---
Control: forwarded -1 https://github.com/avast-tl/retdec/pull/102
Patch merged by upstream. Yet this package is going to be RMed, see #888065.
--- End Message ---
