Arch Linux User Repository

@MartinDiehl: is there any update/fix in the works on the gpart binary name conflict @greyltc mentioned?

The file usr/bin/gpart provided by this package conflicts with that provided by the official gpart package https://archlinux.org/packages/extra/x86_64/gpart/

@medaminezghal: Pls. don't flag as out-of-date

The change you suggest works because it disables the default compiler flags from /etc/makepkg.conf.

In my case, it contains

CFLAGS="-march=x86-64 -mtune=generic -O2 -pipe -fno-plt -fexceptions \
        -Wp,-D_FORTIFY_SOURCE=3 -Wformat -Werror=format-security \
        -fstack-clash-protection -fcf-protection \
        -fno-omit-frame-pointer -mno-omit-leaf-frame-pointer"

which probably reveals the issue that the original authors do not detect because they compile without these flags. I'll send them a mail again.

@MartinDiehl I found a solution cmake -S ${pkgname}-v${pkgver} \ -B build \ -D CMAKE_INSTALL_PREFIX:PATH=/usr \ -D CMAKE_BUILD_TYPE:STRING=Release \ -D BUILD_SHARED_LIBS:BOOL=ON \ -D INSTALL_METIS_HEADERS:BOOL=OFF \ -D COMMON_PTHREAD_FILE:BOOL=ON \ -D SCOTCH_PTHREAD:BOOL=ON \ -D SCOTCH_PTHREAD_MPI:BOOL=ON \ -D COMMON_PTHREAD_AFFINITY_LINUX:BOOL=ON\ -D CMAKE_C_FLAGS:STRING="-fsanitize=undefined" \ -D CMAKE_CXX_FLAGS:STRING="-fsanitize=undefined" \ -D CMAKE_EXE_LINKER_FLAGS:STRING="-fsanitize=undefined" make -C build I test it and it work well

For anyone who is having trouble with the package, especially if you need it for openfoam. If the tests fail you can pass the --nocheck flag and it work fine. If you are using yay (like me) you can do this by adding --mflags="--nocheck" to the command. This is also applicable if you are trying to install openfoam, it will pass the flag to the dependencies as well. Of course the scotch-git works as well, but I think it's because it doesn't run the tests so it's essentially the same. I might be wrong though.

Hope this helps.

scotch-git worked for me alternative while this is getting fixed

All tests passing here. Please don't disable them.

@MartinDiehl: Did you build the package in a clean chroot? What is your environment otherwise?

I've got these failed tests for 7.0.5:

The following tests FAILED:
      8 - test_libesmumps_1 (Subprocess aborted)
      9 - test_libesmumps_2 (Subprocess aborted)
     11 - test_libmetisv3_2 (Subprocess aborted)
     14 - test_libmetis_dual_f_v3 (Subprocess aborted)
     16 - test_libmetisv5_2 (Subprocess aborted)
     19 - test_libmetis_dual_f_v5 (Subprocess aborted)
     34 - test_scotch_graph_2 (Subprocess aborted)
     36 - test_scotch_graph_4 (Subprocess aborted)
     38 - test_scotch_graph_map_copy_2 (Subprocess aborted)
     40 - test_scotch_graph_order_2 (Subprocess aborted)
     42 - test_scotch_graph_part_ovl_2 (Subprocess aborted)
     49 - test_scotch_dgraph_coarsen_bump_b100000 (Failed)
     50 - test_scotch_dgraph_coarsen_m4x4_b1 (Failed)
    101 - gord_bump_b1 (Subprocess aborted)
    102 - gord_cmplx (Subprocess aborted)
    104 - gord_ship001 (Subprocess aborted)
    106 - gotst_bump_b1 (Failed)
    108 - gotst_ship001 (Failed)
    116 - gpart_2 (Subprocess aborted)
    117 - gpart_cluster_1 (Failed)
    119 - gpart_overlap_1 (Failed)
    130 - dgord_2 (Failed)
    133 - dgpart_2 (Failed)
Errors while running CTest

@xantares: You still get failing tests? I'm currently traveling and only have access to the machine where all tests passed for 7.0.4. 7.0.5 is also ok.

Wouldn't it make sense to keep the tests and let people look up this discussion and disable the tests themselves? It only requires the --nocheck option, but at least hints users to potential issues when using scotch.

hi, could you disable the tests for now ?