diff options
Diffstat (limited to 'open_issues/libmachuser_libhurduser_rpc_stubs.mdwn')
| -rw-r--r-- | open_issues/libmachuser_libhurduser_rpc_stubs.mdwn | 26 |
1 files changed, 26 insertions, 0 deletions
diff --git a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn index 670c82cb..11bebd6e 100644 --- a/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn +++ b/open_issues/libmachuser_libhurduser_rpc_stubs.mdwn @@ -133,3 +133,29 @@ License|/fdl]]."]]"""]] <braunr> (imo, the mach_debug interface should be adjusted to be used with privileged ports only) <braunr> (well, maybe not all mach_debug RPCs) + + +# `gnumach.defs` + +[[!message-id +"CAEvUa7nd2LSUsMG9axCx5FeaD1aBvNxE4JMBe95b9hbpdqiLdw@mail.gmail.com"]]. + + +## IRC, freenode, #hurd, 2013-05-13 + + <braunr> youpi: what's the point of the last commit in the upstream hurd + repository (utils/vmstat: Use gnumach.defs from gnumach) ? + <braunr> or rather, i think i see the point, but then why do it only for + gnumach and not fot the rest ? + <braunr> for* + <youpi> most probably because nobody did it, probably + <braunr> aiui, it makes the hurd build process not rely on system headers + <youpi> (and nobody had any issue with it) + <braunr> well yes, that's why i'm wondering :) + <braunr> it looks perfectly fine to me to use system headers instead of + generating them + <youpi> ah right + <youpi> I thought there was actually a reason + <youpi> I'll revert + <youpi> could you answer David about it? + <braunr> sure |