Arch Linux User Repository

@Xoepe, Can you provide more details? I just tried compiling on a clean install and it works as expected. Can you see if its possible to compile the code per the instructions on GitHub?

This is failing to build. It just finished building citnames_a and it outputs the following:

make[3]: *** [Makefile:160: all] Error 2
make[2]: *** [CMakeFiles/BearSource.dir/build.make:134: subprojects/Stamp/BearSource-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:250: CMakeFiles/BearSource.dir/all] Error 2 
make: *** [Makefile:171: all] Error 2

There has been some major changes in the build process for 3.0.0. Specifically, the way it is set up really doesn't like being wrapped in a PKGBUILD. Right now the program should build and run as expected. I will try to pinpoint the issues at a later date.

Flags that have issues are:

In CXXFLAGS: -fno-plt

In LDFLAGS: -z,now

I was getting some test failures when trying to build 2.3.13, which I resolved by disabling ccache (add !ccache to the options array in the PKGBUILD).

On my machine, 2.4.0 builds and checks fine after this fix.

Hey folks, I'm trying to get this updated, but I'm seeing test failures with the new version (the PKGBUILD is configured to run the tests) that probably need to be resolved first.

Hi,

I believe python-pycodestyle and python-coverage might be madedepends

@raul_l: using lib64 does not work as lib64 is a symlink (which collides on install of a package trying to use lib64 as a directory)

For this package, it appears that using lib as CMAKE_INSTALL_LIBDIR works around the bug in it's CMakeLists.txt.

@DanielRichtmann: it is an upstream bug (using ${CMAKE_INSTALL_LIBDIR} like that is incorrect), but it's one we can workaround here.

Thank you both for looking into this issue.

With the latest version I get the ..from LD_PRELOAD cannot be preloaded.. error. It appears to me that CMAKE_INSTALL_LIBDIR should be given as a relative path,

CMAKE_INSTALL_LIBDIR=lib

Or I can just leave out that variable (defaults to lib64 in my case), which also works.

I just upgraded to 2.3.13 and stumbled across the following which prevents me from running bear without specifying the path to libear explicitly:

From PKGBUILD:

CMAKE_INSTALL_PREFIX=/usr
CMAKE_INSTALL_LIBDIR=/usr/lib

From CMakeLists.txt:

set(EAR_LIB_PATH "${CMAKE_INSTALL_LIBDIR}/bear")
set(DEFAULT_PRELOAD_FILE ${CMAKE_INSTALL_PREFIX}/${EAR_LIB_PATH}/${EAR_LIB_FILE} CACHE STRING "Default path to libear.")

Combining these, we get DEFAULT_PRELOAD_FILE equal to /usr//usr/lib/bear/libear.so.

Is this an issue in the PKGBUILD or should I submit an issue upstream?

Interesting. It compiles fine on my system.