Build failure: libatomic_ops (Bug #360)


Added by Tommy Boatman over 1 year ago. Updated 4 months ago.


Status:Closed Start date:02/11/2012
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Libs
Target version:-
Grimoire:Stable

Description

Compile log for libatomic_ops 7.1 Built on Sat Feb 11 20:28:39 UTC 2012
Using gcc version: 4.6.1
Building libatomic_ops
Building in dir: /usr/src/ivmai-libatomic_ops-3bb7644
libatomic_ops 7.1

/var/lib/sorcery/modules/build_api/api2: line 334: ./configure: No such file or directory
! Problem Detected !


Related issues

blocks Grimoire - Bug #424: [stable 0-61.3 cast failures] Master Bug New 08/05/2012

History

Updated by Tommy Boatman over 1 year ago

Note also that there is a hash failure...

Found source file /var/spool/sorcery/libatomic_ops-7.1.tar.gz for spell libatomic_ops in /var/spool/sorcery
Waiting for any Solo casts to complete...
Waiting for any other casts of libatomic_ops to complete... done.
Staging enabled
castfs: checking sanity of <mnt-dir> and <stage-dir>
castfs: stagedir is okay!
Preparing libatomic_ops
Hash checking source file libatomic_ops-7.1.tar.gz...
sha512 check failed!
e5ba1e14d72a2aa85ef0db18026095e4d1490bf31af437ab875ef356b77c7fe9194c6d198c0110db911dd1e8235772c4026dc8f4eecebf8d5be8424837734717 (computed) != 3123457e939e3e02729ad15bb293d2ff358d7157a2772be53769500982bed89a0eda27d9c375e05a6a4c84a3fd7f05aec19ae8064426143c7e773a851b293909 (expected)!
Hash verification failure
Abort? [y]

Updated by Treeve Jelbert over 1 year ago

I still had the original tarball and have just downloaded a new one.
the new sha512 matches what you reported.

A diff of the two sets of files shows no differences.
However the new tarball unpacks to a different directory ivmai-libatomic_ops-ee242b7

This seems to occur frequently when downloading from github
It appears that tarballs are regenerated from time to time. The directory name may be related to a commit id in the tree

Updated by Tommy Boatman 11 months ago

7.2 in test works. Considering this resolved.

  • Status changed from New to Resolved

Updated by Vlad Glagolev 4 months ago

Closing the bug.

  • Status changed from Resolved to Closed

Also available in: Atom PDF