9libs is the Linux code to emulate Plan9. As currently built by the 9libs ebuild, it creates some Plan9 C headers in /usr/include. (Under the non-Gentoo default, these includes would go into /usr/local/include.) The files are libc.h, libg.h, frame.h, regexp.h, and u.h. Should the C headers go into /usr/include/plan9 instead of /usr/include? If so, its seems to me that the 9libs-1.0/include/Makefile.am should have a different definition for execincludedir. I wonder if any of these files collide with standard C headers. I suspect they do, based on bug #17723 and bug #18470. At the very least, something in 9libs seems to be causing problems with libwww and mod_php. That is, if the problem isn't the C headers, then maybe it's something else that ebuilding 9libs causes. I hope this description is sufficient to determine if there is a problem with 9libs. At this time, I don't understand enough about autoconf, automake, etc. to diagnose the problem myself. (But I'm learning!)
yes, it should go into /usr/include/plan9 since it clobbers files in /usr/include/
yes, it broke vim, which I fixed in vim. but now I've noticed it also breaks sane-backends.
Applies to versions: dev-libs/9libs-1.0 media-gfx/sane-backends-1.0.14-r6 libc.h of 9libs is broken. Running gcc main.c -I/usr/lib/9libs/include with >>> #include <libc.h> int main() { return 0; } <<< bails out with: /usr/include/libc.h:33: error: `Rune' has not been declared <libc.h> is missing #include directive for <u.h> which declares `Rune'. This patch for libc.h solves the problem with 9libs. >>> --- libc.h 2004-11-13 16:41:47.567491200 +0100 +++ libc.h 2004-11-13 16:42:08.556300416 +0100 @@ -2,6 +2,8 @@ /* Plan 9 C library interface */ +#include <u.h> + #define dup(a,b) dup2(a,b) #define seek(a,b,c) lseek(a,b,c) #define create(name, mode, perm) creat(name, perm) <<< Also sane-backends will compile cleanly then; their error was: In file included from fujitsu.c:173: /usr/include/libc.h:33: error: parse error before "Rune" Hope that helps. If this is the wrong bugzilla for this bug then pease excuse me.
No idea if this is still an issue, reassigning.
should be all set now
