Libtool

Libtool

[Andreas Enge]

Hello,

I need a newer libtool, and thought it would have to go into core-updates. But:
$ guix refresh -l libtool
Building the following 93 packages would ensure 162 dependent packages are rebuilt

So should I update in master instead?

Andreas

Re: Libtool

[Ludovic Courtès]

Andreas Enge <andreas@enge.fr> skribis:

> I need a newer libtool, and thought it would have to go into core-updates. But:
> $ guix refresh -l libtool
> Building the following 93 packages would ensure 162 dependent packages are rebuilt
>
> So should I update in master instead?

core-updates, please: Guile depends on it, and everything depends
on Guile.

(Now, you’ve probably found a good case for Eric to study.  ;-))

Ludo’.

Re: Libtool

[Andreas Enge]

On Sun, Nov 09, 2014 at 06:47:19PM +0100, Ludovic Courtès wrote:
> (Now, you’ve probably found a good case for Eric to study.  ;-))

I have another one:

$ guix refresh -l acl
Building the following 95 packages would ensure 195 dependent packages are rebuilt

Andreas

Re: Libtool

[Andreas Enge]

[-- Attachment #1: Type: text/plain, Size: 784 bytes --]

The test suite has been rewritten, the patches do not apply any more, and
some of the tests they disabled do not seem to exist any more. The current
test results are:
ERROR: 137 tests were run,
66 failed (59 expected failures).
32 tests were skipped.

So there are 7 failed tests now. I am attaching the testsuite.log and leave
it to the specialists (Ludovic?) to decide whether they fall into the same
category as the previously disabled tests.

Also the NEWS file speaks about tests:
  - The legacy tests have all been migrated to the Autotest harness.
  - The Autotest testsuite can be run without the especially time consuming
    tests with:
        make check-local TESTSUITEFLAGS='-k "!expensive"'

So I wonder whether the 'pre-check phase should not be dropped now.

Andreas


[-- Attachment #2: testsuite.log.bz2 --]
[-- Type: application/octet-stream, Size: 23524 bytes --]

Re: Libtool

[Eric Bavier]

Ludovic Courtès writes:

> Andreas Enge <andreas@enge.fr> skribis:
>
>> I need a newer libtool, and thought it would have to go into core-updates. But:
>> $ guix refresh -l libtool
>> Building the following 93 packages would ensure 162 dependent packages are rebuilt
>>
>> So should I update in master instead?
>
> core-updates, please: Guile depends on it, and everything depends
> on Guile.
>
> (Now, you’ve probably found a good case for Eric to study.  ;-))

The dependents count for libtool would probably be fixed with my
yet-to-be-pushed rewrite with the bags API.  I'm still working out some
kinks with the bootstrap packages, but should have something soon :)

-- 
Eric Bavier

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

Re: Libtool

[Ludovic Courtès]

I’ve finally updated Libtool (commit e13f715).  The test failures turned
out to be just the same as before, plus a couple of others due to the
fact that some tests now need autoconf and automake.

However, I haven’t ported the MIPS patch.

I would like to make this version of Libtool the default in
core-updates, but that needs to work on MIPS before we can do that.
Mark?

Thanks,
Ludo’.