reproduce-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #62700] lzma/xz compilation bug for cmake in Maneage 27ff6f7


From: Boud Roukema
Subject: [bug #62700] lzma/xz compilation bug for cmake in Maneage 27ff6f7
Date: Sun, 3 Jul 2022 13:37:03 -0400 (EDT)

URL:
  <https://savannah.nongnu.org/bugs/?62700>

                 Summary: lzma/xz compilation bug for cmake in Maneage 27ff6f7
                 Project: Maneage
               Submitter: boud
               Submitted: Sun 03 Jul 2022 05:37:02 PM UTC
                Category: Software
                Severity: 3 - Normal
              Item Group: Crash
                  Status: None
                 Privacy: Public
             Assigned to: None
             Open/Closed: Open
         Discussion Lock: Any


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Sun 03 Jul 2022 05:37:02 PM UTC By: Boud Roukema <boud>
SYSTEM:

Linux 3.10.0-1160.36.2.el7.x86_64 #1 SMP Wed Jul 21 11:57:15 UTC 2021 x86_64
x86_64 x86_64 GNU/Linux

CentOS Linux release 7.9.2009 (Core)

initial gcc on the host: 10.2.0

env variables set in startup script sent to slurm:

LD_LIBRARY_PATH=/opt/exp_soft/local/generic/gcc/10.2.0/lib/gcc/x86_64-pc-linux-gnu/10.2.0:/opt/exp_soft/local/generic/gcc/10.2.0/lib64:/opt/exp_soft/local/generic/gcc/10.2.0/lib
LDFLAGS=-L/opt/exp_soft/local/generic/gcc/10.2.0/lib/gcc/x86_64-pc-linux-gnu/10.2.0
-L/opt/exp_soft/local/generic/gcc/10.2.0/lib64
-L/opt/exp_soft/local/generic/gcc/10.2.0/lib
CFLAGS=-I/opt/exp_soft/local/generic/gcc/10.2.0/include


maneage source: maneage-27ff6f7-git.bundle
https://git.maneage.org/project.git/commit/?id=27ff6f7d57ebdd3d3051040b982c1976f990c6e1


KEY LINES OF BUG:

...
make[3]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
[100%] Built target pseudo_cpplint
make[3]: Entering directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
Consolidate compiler generated dependencies of target pseudo_tidy
make[3]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
[100%] Built target pseudo_tidy
make[3]: Entering directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
Consolidate compiler generated dependencies of target pseudo_iwyu
make[3]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
[100%] Built target pseudo_iwyu
make[3]: Entering directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
Consolidate compiler generated dependencies of target foo
make[3]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
[100%] Built target foo
make[2]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'
Install the project...
bin/cmake: /BUILD/software/installed/lib/liblzma.so.5: version `XZ_5.2.2' not
found (required by bin/cmake)
bin/cmake: /BUILD/software/installed/lib/liblzma.so.5: version `XZ_5.1.2alpha'
not found (required by bin/cmake)
make[1]: *** [Makefile:144: install] Error 1
make[1]: Leaving directory
'/dev/shm/24623915-maneage-27ff6f7-git-boud/cmake-3.21.4'



FULL LOG:
full log file
<https://drop.infini.fr/r/1C688pWEac#B6PsrpJZNe7ko+8ZVdxBDh7bHp+WJbqObGLMIT5Bt3o=>


CLUES:
It seems like this is a known bug for Redhat systems [1][2] since 2017.
This gives at least two puzzles:

(1) Why hasn't the fix been upstreamed to xz? (hypothesis:
because this is a one-person email-or-irc-bug-report maintained program; see
MAINTAINABILITY below)

(2) Why does maneage compiling _cmake_ have a problem with the _lzma_
library api on a redhat machine but not on another machine, since
high-level software should be isolated from OS-dependent library
apis like this?

On a machine on which a merge with 27ff6f7 compiled successfully,

$ ldd .local/bin/cmake |grep lzma
liblzma.so.5 => /BUILD/software/installed/lib/liblzma.so.5
(0x00XXXXXXXXXXXXXX)


It is also possible that the patch proposed in [2] itself creates a 
bug on redhat systems [3], as of a report in 2022, per Easybuild [4]
users/developers.

[1]
https://stackoverflow.com/questions/47633870/rpm-lib64-liblzma-so-5-version-xz-5-1-2alpha-not-found-required-by-lib-li
[2] https://github.com/easybuilders/easybuild-easyconfigs/issues/4036
[3] https://github.com/easybuilders/easybuild-easyconfigs/issues/14991
[4] https://github.com/easybuilders/easybuild-easyconfigs

The relation between xz and lzma is not clear to me - understanding this may
help for finding a portable, safe solution. 


MAINTAINABILITY of xz:

The [https://git.tukaani.org/?p=xz.git;a=blob_plain;f=README;hb=HEAD
README] file of _xz_ says "Report your bug via email or IRC (see
Contact information below)." This means that if the main developer
is busy or ill, the community cannot fix the bugs without creating
its own fork, e.g. on a git repository.









    _______________________________________________________

Reply to this item at:

  <https://savannah.nongnu.org/bugs/?62700>

_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/




reply via email to

[Prev in Thread] Current Thread [Next in Thread]