From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: lispf4 fixes. Date: Wed, 05 Oct 2016 09:27:48 +0000 Message-ID: <87k2dn2lij.fsf@we.make.ritual.n0.is> References: <20161004223322.19523-1-ngillmann@runbox.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:41211) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1briUq-0008AJ-29 for guix-devel@gnu.org; Wed, 05 Oct 2016 05:28:16 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1briUm-0004hc-SQ for guix-devel@gnu.org; Wed, 05 Oct 2016 05:28:16 -0400 Received: from aibo.runbox.com ([91.220.196.211]:52276) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1briUm-0004hM-L5 for guix-devel@gnu.org; Wed, 05 Oct 2016 05:28:12 -0400 Received: from [10.9.9.210] (helo=mailfront10.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1briUl-0004Uz-84 for guix-devel@gnu.org; Wed, 05 Oct 2016 11:28:11 +0200 Received: from x5d83fa6c.dyn.telefonica.de ([93.131.250.108] helo=localhost) by mailfront10.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1briUQ-000108-9t for guix-devel@gnu.org; Wed, 05 Oct 2016 11:27:50 +0200 In-Reply-To: <20161004223322.19523-1-ngillmann@runbox.com> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org ng0 writes: > [PATCH 1/2] gnu: lispf4: Remove prebuilt binaries. > > This patch can be applied, it is finished. > > [PATCH 2/2] gnu: lispf4: Fix the searchpath for SYSATOMS. PATCH 2/2 is now: Fix the reference to SYSATOMS, incoming in this thread soon. > This patch requires further input.. The way Ricardo described this > it could be the solution to the SYSATOMS problems (bug #22732) if > someone can write functional C. > If this does not fixes it in the end, I would consider the little > help upstream wants to provide in fixing this and just drop lispf4. > https://github.com/blakemcbride/LISPF4/issues/1 > > --