Arch Linux User Repository

This is a package is also hosted on GitHub.

• Please submit patches and report issues to alice-vision/github.com

• Travis CI Status: <img alt="Build Status" src="https://travis-ci.org/bartoszek/AUR-alice-vision.svg?branch=master" />

Use env vars to control build process:

• CUDA_ARCH="xx yy" to build for a specific Cuda arch, supports multiple values.
• DISABLE_CUDA=1 disable cuda depth map module. (also disables popsift and ute)
• DISABLE_POPSIFT=1 disable gpu accelerated feature matching.
• DISABLE_UTE=1 disable gpu accelerated SFM uncertainty calculation.

Usage cases:

• export DISABLE_CUDA=1 before build
• DISABLE_CUDA=1 ~your-aur-helper~
• makepkg DISABLE_CUDA=1
• yay -S alice-vision --mflags "DISABLE_CUDA=1"

Notice for Yay users:

Since yay relies solely on aur-rpc to solve dependencies instead of calling makepkg --sync it can't follow dependencies logic defined in PKGBUILD. That's why it's up to the user to provide dependencies to enable optional features, otherwise PKGBUILD will silently skip those features.

Optional features:

• popsift: GPU accelerated feature matching.
• uncertainty-framework: GPU accelerated SFM uncertainty calculation.
• cuda: GPU accelerated depth map calculation.

@ultramango : As further disclaimer, building with SFM uncertainty calculation that yields community/magma as dependency. This will break build against cuda:10 as magma packages are build against community/cuda:11 resulting in missing symbols during linking.

@bartus: I tried with DISABLE_POPSIFT=1 and ALICEVISION_USE_POPSIFT=0 and both gave the same error. BUT...

You had a good hunch with PopSift, I recompiled it (using CUDA 10), then build AV again - success. Looks like my PopSift was compiled against CUDA 10 which caused this problem.

Thanks for helping finding the root of it.

@ultramango: Yep it looks like grander issue then I thought at first. Looks like PopSift gets dropped by default and that's why this error doesn't pop up on my system. Will dig further tomorrow (passing DISABLE_POPSIFT=1 to makepkg should build fine)

@bartus: not sure if get it right. Try with CUDA version 10 and 11? For 11 I did:

CUDA_PATH=/opt/cuda makepkg

No change - same error.

And for CUDA version 10 (installed from AUR, separate build path from 11):

CUDA_PATH=/opt/cuda-10.2 makepkg

Fails with some a different error compilation error - /usr/include/c++/10.2.0/type_traits(1396): error: type name is not allowed.

I'll recheck after a reboot just to be sure.

@ultramango: I was able to reproduce this with cuda:10 but with cuda:11 everything builds fine, could you confirm.

Edit: symbol is defined in popsift

scanelf -ARs __fatbinwrap_38_cuda_device_runtime_compute_86_cpp1_ii_8b1a5d37 -q . /opt/cuda/ /usr/lib
__fatbinwrap_38_cuda_device_runtime_compute_86_cpp1_ii_8b1a5d37  ./Linux-x86_64/libaliceVision_feature.so.2.3
__fatbinwrap_38_cuda_device_runtime_compute_86_cpp1_ii_8b1a5d37  /usr/lib/libpopsift.a:popsift_intermediate_link.o

@bartus: thanks, indeed nowhere to find. I'll keep digging, as I mentioned, must be something specific. I'll check for some global (build) options that might have set in the past.

Edit: after disabling parallel make (MAKEFLAGS) in /etc/makepkg.conf it fails at different step with the same error.

Edit 2: submitted to upstream: https://github.com/alicevision/AliceVision/issues/974

@ultramango: Can't find this symbol on my system.

Try scanning you system with scanelf both for /opt/cuda and for alice-vision build dir.

scanelf -qRs +__fatbinwrap_38_cuda_device_runtime_compute_75_cpp1_ii_8b1a5d37 /opt/cuda ((alice vision build path))

Anyone else having a problem with linking? If fails for me at this stage:

[283/465] Linking CXX executable Linux-x86_64/aliceVision_panoramaWarping-1.0

With undefined reference to __fatbinwrap_38_cuda_device_runtime_compute_75_cpp1_ii_8b1a5d37. I suspect there's something specific to my system that it fails to add CUDA libraries to linking (at least -lcudart).

FYI there's an upstream issue with zen 3 cpus where it can't identify the CPU type and falls back to generic which disables sse2 which causes it to fail to build

@hrehfeld, @kureta: patched