From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: clisp executable images fail at startup Date: Sat, 31 Dec 2016 20:41:34 +0100 Message-ID: <87o9zrzy1d.fsf@elephly.net> References: <8760m9ya4z.fsf@elephly.net> <8737h57zuu.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:40173) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cNPXG-0007sA-HH for help-guix@gnu.org; Sat, 31 Dec 2016 14:41:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cNPXD-0001T3-Bw for help-guix@gnu.org; Sat, 31 Dec 2016 14:41:46 -0500 In-reply-to: <8737h57zuu.fsf@gnu.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: Ludovic =?utf-8?Q?Court=C3=A8s?= Cc: help-guix Ludovic Courtès writes: >> When I packaged it and tried to run the packaged executable, however, I >> got this error: >> >> module 'syscalls' requires package OS. >> >> (This error is reported by CLISP.) > > Could it be a search path issue? Did you try strace’ing clisp to see > where it’s looking for “OS”? I couldn’t find anything of interest by strace’ing the binary, but I noticed that the binary I built locally is an order of magnitude larger than the binary that ended up in the store (21MB instead of 2.6MB). Turns out that after disabling stripping I get an executable that works fine. Maybe executable CLISP images should never be stripped. -- Ricardo GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC http://elephly.net