http://oss.sgi.com/bugzilla/show_bug.cgi?id=786
------- Additional Comments From kelledin@xxxxxxxxxxxx 2008-07-20 19:44 CST
-------
True, it looks like <sys/syscall.h> provides these defines, and they *are*
correct. So that would probably be a better solution. So I'd have to wonder
why libattr is off defining the syscall numbers on its own?
Probably a better approach would be to #include <sys/syscall.h>, then fall back
on the built-in definitions if they aren't already defined? And perhaps put in
a configure check to make sure we actually have the header.
In any event, the built-in syscall macros should either be correct, or they
should be removed. I'd prefer if libattr loudly failed to compile rather than
silently compile with bad syscall values, then perform off-the-wall,
possibly-destructive actions at run-time.
--
Configure bugmail: http://oss.sgi.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
|