On 2018 Jan 21 (Sun) at 21:45:53 +0100 (+0100), Jeremie Courreges-Anglas wrote:
:On Sun, Jan 21 2018, Brian Callahan <[email protected]> wrote:
:> On 01/21/18 08:13, Peter Hessler wrote:
:>> On 2018 Jan 21 (Sun) at 02:06:52 -0500 (-0500), Brian Callahan wrote:
:>> :Finally, it looks like libffi needs libc++abi on arm for at least some
:>> :functions, as
:>> :experienced with lang/snobol4, its configure script didn't pick up libffi
and
:>> :instead
:>> :complained about this:
:>> :/usr/local/lib/libffi.so.1.2: undefined reference to
`__aeabi_unwind_cpp_pr0'
:>> :/usr/local/lib/libffi.so.1.2: undefined reference to
`__aeabi_unwind_cpp_pr1'
:>> :Those functions are in libc++abi.
:>> :
:>>
:>> Did you mean to include a patch to libffi.pc to address these issues?
:>>
:>>
:>
:> Ugh. No more 2am diffs more me.
:>
:> We just want this to be for arm, of course, to avoid breaking all gcc
:> archs. Attached diff deals.
:
:I think it would be better to link libffi against -lc++abi, inter-libs deps
:would be enough and would ensure that consumers don't need to use
:pkg-config. static builds would still need the pkg-config goo, but we
:don't have static archs any more. Do we have such ports?
:
iirc, lld doesn't do inter-lib deps so we would still need pkg-config
help. while this isn't a problem *yet*, I'd like to avoid it being a
problem in the (hopefully near) future.
--
Corruption is not the #1 priority of the Police Commissioner. His job
is to enforce the law and fight crime.
-- P.B.A. President E. J. Kiernan
