To OpenBSD ports list,
I can't start OpenBSD's amd64 snapshot package of supertux-0.6.0p0.
Are other people getting the same error? I get
opa$ supertux2
[FATAL] /usr/obj/ports/supertux-0.6.0/SuperTux-v0.6.0-Source/src/supertux/main.c
pp:601 Unexpected exception: boost::filesystem::status: Permission denied: "/usr
/obj/ports/supertux-0.6.0/SuperTux-v0.6.0-Source/data/credits.stxt"
opa$ ls -ld /usr/obj
drwxrwx--- 2 build wobj 512 Nov 20 19:58 /usr/obj
I know from Landry Brueil's last powerpc bulk [1] that arches with
ports-gcc 4.9 can't build supertux. My powerpc machine is using
ports-gcc 8 (instead of the default 4.9) and has built and packaged
supertux, so the switch from 4.9 to 8 solves that problem.
My powerpc machine can't start supertux, because
ghostborough$ supertux2
supertux2:/usr/lib/libstdc++.so.57.0: /usr/local/lib/libestdc++.so.19.0 : WARNIN
G: symbol(_ZNSt6locale5_Impl11_S_id_ctypeE) size mismatch, relink your program
[FATAL] /usr/ports/pobj/supertux-0.6.0/SuperTux-v0.6.0-Source/src/supertux/main.
cpp:601 Unexpected exception: boost::filesystem::canonical: No such file or dire
ctory: "/home/kernigh/${PREFIX}/share/supertux2"
I ignore the "size mismatch", because it means that ports-gcc built
supertux and base-gcc built some C++ libraries in xenocara.
I see how patch-src_supertux_main_cpp adds ${PREFIX}, but don't see
how ${PREFIX} gets expanded. One might need to add a pre-configure
target like in some other ports:
pre-configure:
${SUBST_CMD} ${WRKSRC}/src/supertux/main.cpp
I went to my amd64 vm to check whether the amd64 snapshot package
gives the ${PREFIX} error, but I got the /usr/obj error. (I connected
to my vm with ssh -Y; there's no accelerated OpenGL, so supertux would
run slow if it did start.) Now I don't know whether we need a
pre-configure target.
[1] http://build-failures.rhaalovely.net//powerpc/2019-03-04/games/supertux.log
--
George Koehler <[email protected]>
