From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: Andreas Enge <andreas@enge.fr>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: libarchive fails tests on i686
Date: Thu, 5 Mar 2015 23:54:42 +0100 [thread overview]
Message-ID: <87mw3r837x.fsf@mango.localdomain> (raw)
In-Reply-To: <20150305101739.GA9200@debian.eduroam.u-bordeaux.fr>
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
next prev parent reply other threads:[~2015-03-05 22:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-05 9:47 libarchive fails tests on i686 Ricardo Wurmus
2015-03-05 10:17 ` Andreas Enge
2015-03-05 22:54 ` Ricardo Wurmus [this message]
2015-03-05 23:18 ` Andreas Enge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mw3r837x.fsf@mango.localdomain \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=andreas@enge.fr \
--cc=guix-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).