Talk:Testing

From OpenMW Wiki
Jump to: navigation, search

MacOS X errors

Followup to Talk:Development Environment Setup#Mac instructions, where no one responded (there's much more detail over there; this post is just about trying again in 0.43).

In MacOS X (or macOS or whatever it's named now) 10.13.2, I'm getting a long series of errors like these when I try doing gdb ./openmw:

This GDB was configured as "x86_64-apple-darwin"...unable to read unknown load command 0x80000028

Reading symbols for shared libraries ........
warning: Could not find object file "/Users/nkasyanov/Projects/openmw/openmw-deps/src/boost/bin.v2/libs/system/build/darwin-4.2.1/release/threading-multi/error_code.o" - no debug information available for "error_code.cpp".

.
warning: Could not find object file "/Users/nkasyanov/Projects/openmw/openmw-deps/src/boost/bin.v2/libs/filesystem/build/darwin-4.2.1/release/threading-multi/codecvt_error_category.o" - no debug information available for "codecvt_error_category.cpp".


warning: Could not find object file "/Users/nkasyanov/Projects/openmw/openmw-deps/src/boost/bin.v2/libs/filesystem/build/darwin-4.2.1/release/threading-multi/operations.o" - no debug information available for "operations.cpp".

and so on. This is all gibberish to me, other than that clearly the macOS nightly builds have someone's username hardcoded into them (I am not nkasyanov, and am not sure who to get that person's attention. I thought I'd IDed who they were on the bug tracker, but did not get a response (after 6+ months).

If I try run --no-grab anyway, I get:

assertion failure on line 243 of "/SourceCache/gdb/gdb-1708/src/gdb/macosx/macosx-nat-inferior-util.c" in function "kern_return_t macosx_inferior_resume_mach(macosx_inferior_status *, int)": macosx_task_valid (s->task)

As reported at Talk:Development Environment Setup#Mac instructions, I've researched and tried everything I can think of to work around this, and cannot get the instructions on how to set up one's own compiled copy to work; they seem entirely dependent on having a vanilla Apple set of tools and will have cascading failures if you're using MacPorts or some other source of Unix binaries. Someone did report having it work okay for them while using Homebrew, but my guess is their Homebrew did not replace anything the build depends on. Even the pre-compiled dependencies package is a FAIL for me. I can't produce the crash.log files that people want. — Darklocq  ¢ 13:37, 5 March 2018 (CET)