The user-specific part of procinfo has a helper function that makes a syscall. That was implying __ros_syscall_errno() existed. Ideally, we wouldn't do that, but doing otherwise causes include loops.
Alternatively, we could just move or remove the functions. Considering they are for debugging, just externing in the function seems fine. Reinstall your kernel headers. Signed-off-by: Barret Rhoden <[email protected]> --- kern/include/ros/procinfo.h | 3 +++ 1 file changed, 3 insertions(+) diff --git a/kern/include/ros/procinfo.h b/kern/include/ros/procinfo.h index 26a836352178..611626c6e304 100644 --- a/kern/include/ros/procinfo.h +++ b/kern/include/ros/procinfo.h @@ -93,6 +93,9 @@ static inline uint32_t __get_vcoreid_from_procinfo(void) * there is a 'memory barrier' between the IPI write and the seqctr write. * I think this is true. */ uint32_t kpcoreid, kvcoreid; + extern long __ros_syscall_noerrno(unsigned int _num, long _a0, long _a1, + long _a2, long _a3, long _a4, long _a5); + seq_ctr_t old_seq; do { cmb(); -- 2.7.0.rc3.207.g0ac5344 -- You received this message because you are subscribed to the Google Groups "Akaros" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
