On 2019-08-21, Stuart Henderson <s...@spacehopper.org> wrote:
>> > * If you build ghidra on a system where gcc/g++/libstdc++ are
>> > available, it does indeed link something against libstdc++ and
>> > port-lib-depends-check indicates WANTLIB+=stdc++.
>> >
>> > * If you build ghidra on a system where gcc/g++/libstdc++ are NOT
>> > available, it still builds fine, something is linked against
>> > libc++/libc++abi/pthread and port-lib-depends-check consequently
>> > indicates WANTLIB+=${COMPILER_LIBCXX}.
>
> Is this enough? Untested beyond "does it create the right symlink".
>
> --- Makefile 12 Jul 2019 20:49:02 -0000 1.4
> +++ Makefile 21 Aug 2019 08:21:22 -0000
> @@ -39,6 +39,7 @@ post-extract:
> ${WRKSRC}/ghidraRun
> @perl -pi -e 's,#!/bin/bash,#!${LOCALBASE}/bin/bash,' \
> ${WRKSRC}/support/launch.sh
> + ln -s c++ ${WRKDIR}/bin/g++
This actually breaks the build:
> Task :Decompiler:compileDecompileOpenbsd64ExecutableDecompileCpp FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task
':Decompiler:compileDecompileOpenbsd64ExecutableDecompileCpp'.
> java.lang.NullPointerException (no error message)
--
Christian "naddy" Weisgerber na...@mips.inka.de
