From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Enge Subject: Cross-compilation from armhf to mips64el Date: Mon, 5 Oct 2015 21:08:38 +0200 Message-ID: <20151005190838.GA5006@debian> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52900) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjB7v-0002Tv-Js for guix-devel@gnu.org; Mon, 05 Oct 2015 15:08:48 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZjB7s-00076Z-Ep for guix-devel@gnu.org; Mon, 05 Oct 2015 15:08:47 -0400 Received: from mout.kundenserver.de ([212.227.17.24]:50663) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZjB7s-00075z-5r for guix-devel@gnu.org; Mon, 05 Oct 2015 15:08:44 -0400 Content-Disposition: inline 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-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel@gnu.org Hello, currently, we get lots of failed jobs for armhf coming from cross-compilation, such as http://hydra.gnu.org/job/gnu/master/mips64el-linux-gnu.grep-2.21.armhf-linux I would think that the problem comes from build-aux/hydra/guix.scm, in this function: (define (from-32-to-64? target) ;; Return true if SYSTEM is 32-bit and TARGET is 64-bit. This hack ;; prevents known-to-fail cross-builds from i686-linux or armhf-linux to ;; mips64el-linux-gnuabi64. (and (or (string-prefix? "i686-" system) (string-prefix? "armhf-" system)) (string-suffix? "64" target))) since target seems to be mips64el-linux-gnu and not mips64el-linux-gnuabi64. Then I would replace "string-suffix?" by "string-contains". But I must have overlooked something, since hydra does not cross-build from i686 to mips. If someone could have a look... Andreas