all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: libarchive fails tests on i686
Date: Fri, 6 Mar 2015 00:18:54 +0100	[thread overview]
Message-ID: <20150305231854.GA31643@debian> (raw)
In-Reply-To: <87mw3r837x.fsf@mango.localdomain>

On Thu, Mar 05, 2015 at 11:54:42PM +0100, Ricardo Wurmus wrote:

> > 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.

In that case, from what I understand, cmake will use its bundled copy, so it
is not a good idea to drop the input.

> 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?

I wondered about this; it is quite probable they behave differently.
But the Makefile calls a test program which I think is bsdtar in this case.

> 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?

Well, I suppose they have no side effects except for disabling the build
of bsdtar and bsdcpio, and I do not see why we would have a use for them
on guix. Cmake itself links to libarchive as shown by "ldd", so it should
not be affected.

Andreas

      reply	other threads:[~2015-03-05 23:19 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
2015-03-05 23:18     ` Andreas Enge [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150305231854.GA31643@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=ricardo.wurmus@mdc-berlin.de \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.