> From: Adam Wolk <adam.w...@koparo.com> > Date: Sat, 18 Apr 2015 23:23:40 +0200 > > Hi tech@, > > I'm working on a port for lang/dart and got stuck on ucontext.h compile > errors. > The first one was quite easy, changing sys/ucontext.h to signal.h since > ucontext_t is > defined there > > sys/signal.h: > typedef struct sigcontext ucontext_t;
It is questionable whether ucontext_t should be defined there. The <sys/ucontext.h> header has been removed from POSIX, but POSIX still refers to ucontext_t in its signal handler description. In the end the reason <sys/ucontext.h> has been removed from POSIX is because it is impossible to use its functionality in a portable fashion. It is inherently architecture dependent, and effectively OS dependent as well. > This allowed me to move forward and stop on the next bit: > In file included from runtime/vm/thread_interrupter.h:9:0, > from runtime/vm/profiler.h:13, > from runtime/vm/dart.ca c:22: > runtime/vm/signal_handler.h:49:44: error: 'mcontext_t' does not name a > type > static uintptr_t GetProgramCounter(const mcontext_t& mcontext); > ^ > runtime/vm/signal_handler.h:50:42: error: 'mcontext_t' does not name a > type If this bit of code is indeed essential,you'll have to write an OpenBSD-specific version of it. My advise would be to stick to using "struct sigcontext". Change GetProgramCounter to take "const struct sigcontext& sc" as an argument, and make it return sc.sc_pc; That would make it work on alpha/i386/sparc/sparc64/vax and we can add the appropriate define on other architectures. For amd64 that would be #define sc_pc sc_rip If you need more help, please post the relevant code or provide an url with (preferabley browsable) source code. > Which lead me to a hunt on how other parts of base/ports handle this. > I grepped /usr/src and found something interesting. > > /gnu/gcc/gcc/config/pa/hpux-unwind.h This is HP-UX specific code.
