Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-18 Thread Ferenc Wágner
Mathieu Malaterre writes: >>> Ferenc Wágner writes: >>> The test looks for the exported API function names in the text (T) section, but the ppc64 nm reports them in the data (D) section: $ nm -B -D libknet.so.1.0.0 A LIBKNET [...] 0003e

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-17 Thread Mathieu Malaterre
Control: tags -1 upstream On Wed, Jan 17, 2018 at 11:32 AM, Mathieu Malaterre wrote: > On Sun, Jan 14, 2018 at 4:47 PM, Aaron M. Ucko wrote: >> Ferenc Wágner writes: >> >>> The test looks for the exported API function names in the text (T) >>> section, but the ppc64 nm reports them in the data

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-17 Thread Mathieu Malaterre
On Sun, Jan 14, 2018 at 4:47 PM, Aaron M. Ucko wrote: > Ferenc Wágner writes: > >> The test looks for the exported API function names in the text (T) >> section, but the ppc64 nm reports them in the data (D) section: >> >> $ nm -B -D libknet.so.1.0.0 >> A LIBKNET >> [...] >>

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-14 Thread Aaron M. Ucko
Ferenc Wágner writes: > The test looks for the exported API function names in the text (T) > section, but the ppc64 nm reports them in the data (D) section: > > $ nm -B -D libknet.so.1.0.0 > A LIBKNET > [...] > 0003ec40 D knet_handle_new > [...] > > Is this a known ppc64

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-14 Thread Ferenc Wágner
u...@debian.org (Aaron M. Ucko) writes: > Ferenc Wágner writes: > >> I wanted to, but hit some problem... Maybe failed to access a >> porterbox. Anyway, that error does not make any sense, knet_handle_new >> is the first thing the tests call, so I assumed it was a toolchain or >> binutils issue

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-12 Thread Aaron M. Ucko
Ferenc Wágner writes: > I wanted to, but hit some problem... Maybe failed to access a > porterbox. Anyway, that error does not make any sense, knet_handle_new > is the first thing the tests call, so I assumed it was a toolchain or > binutils issue which would resolve itself eventually... Ah, o

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-12 Thread Ferenc Wágner
"Aaron M. Ucko" writes: > The build of kronosnet for ppc64 (admittedly not a release > architecture) failed: > > ../../libknet/tests/api-test-coverage ../.. ../.. > Checking for exported symbols NOT available in header file > Checking for symbols in header file NOT exported by binary lib >

Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib

2018-01-11 Thread Aaron M. Ucko
Source: kronosnet Version: 1.0-1 Severity: important Tags: upstream Justification: fails to build from source User: debian-powe...@lists.debian.org Usertags: ppc64 The build of kronosnet for ppc64 (admittedly not a release architecture) failed: ../../libknet/tests/api-test-coverage ../.. ../..