Source: fswatch
Version: 1.10.0+repack-1
Severity: important
Tags: upstream
Justification: fails to build from source

Builds of fswatch for architectures lacking built-in support for
64-bit atomic operations have been failing:

  g++ -DHAVE_CONFIG_H -I. -I../..  -I../../libfswatch/src 
-DLOCALEDIR=\"/usr/share/locale\" -Wdate-time -D_FORTIFY_SOURCE=2  -g -O2 
-fdebug-prefix-map=/<<BUILDDIR>>/fswatch-1.10.0+repack=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -c -o fswatch.o 
fswatch.cpp
  /bin/bash ../../libtool  --tag=CXX   --mode=link g++  -g -O2 
-fdebug-prefix-map=/<<BUILDDIR>>/fswatch-1.10.0+repack=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall  -Wl,-z,relro 
-Wl,-z,now -Wl,--as-needed -o fswatch fswatch.o 
../../libfswatch/src/libfswatch/libfswatch.la  -lc -lpthread 
  libtool: link: g++ -g -O2 
-fdebug-prefix-map=/<<BUILDDIR>>/fswatch-1.10.0+repack=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wall -Wl,-z 
-Wl,relro -Wl,-z -Wl,now -o .libs/fswatch fswatch.o  -Wl,--as-needed 
../../libfswatch/src/libfswatch/.libs/libfswatch.so -lc -lpthread
  ../../libfswatch/src/libfswatch/.libs/libfswatch.so: undefined reference to 
`__atomic_load_8'
  ../../libfswatch/src/libfswatch/.libs/libfswatch.so: undefined reference to 
`__atomic_store_8'
  collect2: error: ld returned 1 exit status
  Makefile:494: recipe for target 'fswatch' failed

I see this error on armel, mips, mipsel, and the non-release
architectures m68k, powerpc, and sh4, but IIRC it could affect other
non-release architectures if and when fswatch's build dependencies
become available there.

To accommodate these architectures, please link against -latomic.
Since you're already using --as-needed, you can list -latomic
unconditionally without having to worry about builds for the remaining
architectures picking up a formal dependency on libatomic.

Thanks!

-- 
Aaron M. Ucko, KB1CJC (amu at alum.mit.edu, ucko at debian.org)
http://www.mit.edu/~amu/ | http://stuff.mit.edu/cgi/finger/?a...@monk.mit.edu

Reply via email to