Re: Bug#886973: kronosnet: FTBFS on ppc64: knet_handle_new not found in binary lib
Mathieu Malaterre <email@example.com> writes:
>>> Ferenc Wágner <firstname.lastname@example.org> 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
>>>> 0000000000000000 A LIBKNET
>>>> 000000000003ec40 D knet_handle_new
>>>> Is this a known ppc64 peculiarity or a binutils bug?
> PowerPC64 ELFv1 ABI defines the address of a function as that of a
> function descriptor defined in .opd, a data section.
> So upstream should relax the nm test a bit to consider "D" section
> also (at least on PPC64). As a side note since the Debian package
> provides a symbol file, I would simply comment out the test...
Thanks for the info, Alan and Mathieu! I'm trying to push the change
upstream (I think it makes sense on other architectures as well).