Source: tcpflow
Version: 1.4.0+repack1-2
Severity: normal

On some arches I see


 g++  -g -pthread -g -O3 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -Wall -MD -D_FORTIFY_SOURCE=2 -Wpointer-arith -Wshadow 
-Wwrite-strings -Wcast-align -Wredundant-decls -Wdisabled-optimization 
-Wfloat-equal -Wmultichar -Wmissing-noreturn -Woverloaded-virtual -Wsign-promo 
-funit-at-a-time -Wstrict-null-sentinel -Weffc++   -L/usr/local/lib 
-Wl,-z,relro -o tcpflow dfxml/src/dfxml_writer.o netviz/plot_view.o 
netviz/time_histogram_view.o netviz/time_histogram.o 
netviz/address_histogram_view.o netviz/address_histogram.o 
netviz/port_histogram_view.o netviz/port_histogram.o netviz/packetfall.o 
netviz/net_map.o netviz/legend_view.o netviz/one_page_report.o 
be13_api/beregex.o be13_api/feature_recorder.o be13_api/feature_recorder_set.o 
be13_api/pcap_fake.o be13_api/plugin.o be13_api/sbuf.o be13_api/sbuf_stream.o 
be13_api/unicode_escape.o be13_api/utils.o wifi_datalink.o wifipcap.o cpack.o 
datalink.o flow.o tcpflow.o tcpip.o tcpdemux.o util.o scan_md5.o
  scan_ht
 tp.o scan_tcpdemux.o scan_netviz.o http-parser/http_parser.o mime_map.o  
-lpcap -lcairo -lfontconfig -lfreetype -lpixman-1 -lexpat  -lssl -lcrypto -lz 
-lssl -lcrypto 
 be13_api/feature_recorder.o: In function `feature_recorder::carve(sbuf_t 
const&, unsigned int, unsigned int, std::basic_string<char, 
std::char_traits<char>, std::allocator<char> > const&, be13::hash_def const&)':
 /«BUILDDIR»/tcpflow-1.4.0+repack1/src/be13_api/feature_recorder.cpp:618: 
undefined reference to `__sync_add_and_fetch_8'
 be13_api/plugin.o: In function `be13::plugin::process_sbuf(scanner_params 
const&)':
 /«BUILDDIR»/tcpflow-1.4.0+repack1/src/be13_api/plugin.cpp:674: undefined 
reference to `__sync_add_and_fetch_8'
 collect2: ld returned 1 exit status

Probably those arches don't support some bit of hardware that 
__sync_add_and_fetch_8() uses.


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]

Reply via email to