From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mathieu Othacehe Subject: Cross-compiling guile libraries Date: Thu, 21 Mar 2019 14:25:05 +0100 Message-ID: <87d0mkpdfy.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([209.51.188.92]:54064) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h6xj6-0001zP-Vn for guix-devel@gnu.org; Thu, 21 Mar 2019 09:27:21 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h6xh0-0000H7-Bl for guix-devel@gnu.org; Thu, 21 Mar 2019 09:25:11 -0400 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 , guile-devel Hello! To be able to add a cross-compilation option to guix-system (see https://lists.gnu.org/archive/html/guix-devel/2019-03/msg00062.html), we need to cross-compile a bunch of guile libraries. Even if guild has a "target" option allowing to cross-compile sources, autotools does not seem to have support for guile cross-compilation. For instance, passing "--host=aarch64-linux-gnu" to configure script doesn't set the "target" argument of guild to the specified triplet. For trivial guile libraries guix has a "guile-build-system" which does the job alright, but I don't think using this build-system for every guile library is a solution. Has anyone already tried to mess with guile.m4 and other stuff in order to cross-compile a guile library via autotools? Thanks, Mathieu