From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ricardo Wurmus Subject: Re: libarchive fails tests on i686 Date: Thu, 5 Mar 2015 23:54:42 +0100 Message-ID: <87mw3r837x.fsf@mango.localdomain> References: <87r3t393na.fsf@mango.localdomain> <20150305101739.GA9200@debian.eduroam.u-bordeaux.fr> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:46257) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTefP-0006pV-RY for guix-devel@gnu.org; Thu, 05 Mar 2015 17:54:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YTefM-0002xo-Jj for guix-devel@gnu.org; Thu, 05 Mar 2015 17:54:55 -0500 Received: from sinope.bbbm.mdc-berlin.de ([141.80.25.23]:39064) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YTefM-0002xJ-AS for guix-devel@gnu.org; Thu, 05 Mar 2015 17:54:52 -0500 In-Reply-To: <20150305101739.GA9200@debian.eduroam.u-bordeaux.fr> 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: Andreas Enge Cc: Guix-devel Andreas Enge writes: > On Thu, Mar 05, 2015 at 10:47:53AM +0100, Ricardo Wurmus wrote: >> libarchive has not yet been built for i686 on hydra, so there are no >> binary substitutes available. The failure to build libarchive blocks >> other packages such as qt. > > It is a bit strange that we should depend on bsdtar and bsdcpio... Well, > probably it is the library libarchive. The dependency comes in through > cmake (and is actually not detected by "guix refresh -l libarchive"). > > In linuxfromscratch, libarchive is only mentioned as "recommended" to build > cmake: > http://www.linuxfromscratch.org/blfs/view/svn/general/cmake.html > So maybe we could take it out from the cmake inputs? I do not know enough about this to decide either way. > Or maybe we should build libarchive with the configure flags > --disable-bsdtar --disable-bsdcpio > (and then the tests would not be run...); after all, we have gnu tar and > gnu cpio. I haven't yet looked more closely at what the tests are trying to establish. Are you suggesting that the tests fail because GNU tar behaves differently? > What do you think? I would like to understand the test failure better, but on the other side this failure blocks a considerable number of packages motivating me to get rid of the problem. I don't know what side effects the above configure flags would have. Could we just disable these tests for now? ~~ Ricardo