https://sourceforge.net/p/clisp/patches/52/2018-02-28T16:47:37.497000ZRecent changes to 52: Fix for compilation on GNU/Hurd2018-02-28T16:47:37.497000Z2018-02-28T16:47:37.497000ZSébastien Villemothttps://sourceforge.net/u/svillemot/https://sourceforge.netece5b5e3dd2a8e86d4939b7b8544bad51766a43b

<div class="markdown_content"><p>Concerning clisp-hurd-einval-extra.patch, I have verified that it is no longer needed on the tip of the clisp-2.50 branch. I am going to drop it from the Debian package. Hence this bug can be closed.</p></div>

2018-01-19T21:04:54.096000Z2018-01-19T21:04:54.096000ZBruno Haiblehttps://sourceforge.net/u/haible/https://sourceforge.nete404c623b85ebcc73bc94fc60e2ab2d0917e38d0

<div class="markdown_content"><p>Chasing the references to<br/> <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801260" rel="nofollow">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801260</a><br/> -&gt; <a href="https://lists.debian.org/debian-hurd/2015/09/msg00031.html" rel="nofollow">https://lists.debian.org/debian-hurd/2015/09/msg00031.html</a><br/> -&gt; <a href="https://buildd.debian.org/status/fetch.php?pkg=clisp&amp;arch=hurd-i386&amp;ver=1%3A2.49-10&amp;stamp=1440769077" rel="nofollow">https://buildd.debian.org/status/fetch.php?pkg=clisp&amp;arch=hurd-i386&amp;ver=1%3A2.49-10&amp;stamp=1440769077</a><br/> this seems indeed to be an interaction with the Debian build system with the file descriptors 0, 1, 2.<br/> On other operating systems, with 'nohup' that clobbers the file descriptor 0, I see similar errors.<br/> So it's perfectly OK for Debian to include this patch.<br/> But upstream != Debian; I won't include it because I haven't seen it happen myself so far and because I would expect to get some "standard" errno such as ENOTTY or EBADF, not EMIG_BAD_ID.</p></div>

2018-01-19T17:17:48.066000Z2018-01-19T17:17:48.066000ZSébastien Villemothttps://sourceforge.net/u/svillemot/https://sourceforge.netde5a096737b95444afa5a09b052b956a94eea805

<div class="markdown_content"><p>About the clisp-hurd-einval-extra.patch: I haven't recently tested that this patch is actually needed.</p> <p>The problem was reported more than 2 years ago, see <a href="https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801260" rel="nofollow">https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801260</a></p> <p>If you confirm that clisp works fine on GNU/Hurd without it, then it's probably ok to just ignore it.</p></div>

2018-01-13T14:14:48.387000Z2018-01-13T14:14:48.387000ZBruno Haiblehttps://sourceforge.net/u/haible/https://sourceforge.net37aa4178260b8bc0012ec0ebd084e3ec1d1f5ccd

<div class="markdown_content"><p>I have applied the equivalent of the maxpathlen.patch; thanks.</p> <p>Regarding clisp-hurd-einval-extra.patch: How to reproduce the issue? I've not seen any related test failure or misbehaviour of clisp on GNU/Hurd in a couple of months. (I'm using Samuel Thibault's Hurd image from 2017-01-15.)</p></div>

2017-12-06T18:25:48.758000Z2017-12-06T18:25:48.758000ZSam Steingoldhttps://sourceforge.net/u/sds/https://sourceforge.net94e557f2365f482d5150f8bf472a5e7f17d0d1c1

<div class="markdown_content"><ul> <li><strong>assigned_to</strong>: Bruno Haible</li> <li><strong>Group</strong>: --&gt; </li> </ul></div>

2017-09-21T15:23:43.504000Z2017-09-21T15:23:43.504000ZSébastien Villemothttps://sourceforge.net/u/svillemot/https://sourceforge.net92f95d6e3f630f580baca440af95c214e40038ae

<div class="markdown_content"><p>Dear CLISP maintainers,</p> <p>Please find attached two patches contributed by Flavio Cruz, that fix the compilation of CLISP on GNU/Hurd. Those patches are going to be applied to the Debian package.</p> <p>More details in the respective patch headers.</p> <p>Best,</p></div>

2017-09-21T15:23:43.504000Z2017-09-21T15:23:43.504000ZSébastien Villemothttps://sourceforge.net/u/svillemot/https://sourceforge.nete1082d83ff294fa2617b5cf17c8d249fed663f42

<div class="markdown_content"><p>Ticket 52 has been modified: Fix for compilation on GNU/Hurd<br/> Edited By: Sam Steingold (sds)<br/> Owner updated: None =&gt; u'haible'</p></div>