[jira] [Commented] (DAEMON-294) Compilation fails on GNU Hurd

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[jira] [Commented] (DAEMON-294) Compilation fails on GNU Hurd

ASF GitHub Bot (Jira)

    [ https://issues.apache.org/jira/browse/DAEMON-294?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13628984#comment-13628984 ]

Emmanuel Bourg commented on DAEMON-294:
---------------------------------------

Actually Hurd is not a variant of Linux, it's a different kernel. It looks like this issue is quite common:

http://www.gnu.org/software/hurd/community/gsoc/project_ideas/maxpath.html

{quote}POSIX describes some constants (or rather macros) like PATH_MAX/MAXPATHLEN and similar, which may be defined by the system to indicate certain limits. Many people overlook the may though: Systems only should define them if they actually have such fixed limits (see limits.h). The Hurd, following the GNU Coding Standards, tries to avoid this kind of arbitrary limits, and consequently doesn't define the macros.{quote}

I'll try to contact the Hurd community to get some help.

               

> Compilation fails on GNU Hurd
> -----------------------------
>
>                 Key: DAEMON-294
>                 URL: https://issues.apache.org/jira/browse/DAEMON-294
>             Project: Commons Daemon
>          Issue Type: Bug
>    Affects Versions: 1.0.10
>            Reporter: Emmanuel Bourg
>            Priority: Minor
>
> The compilation of Commons Daemon fails on GNU Hurd as reported by the buildd instance used by Debian. It breaks with the following error:
> {code}arguments.c:61:17: error: 'PATH_MAX' undeclared (first use in this function){code}
> The full report is available here:
> https://buildd.debian.org/status/package.php?p=commons-daemon
> https://buildd.debian.org/status/fetch.php?pkg=commons-daemon&arch=hurd-i386&ver=1.0.10-3&stamp=1345183045

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira