Skip to contentSkip to conversation

New: man fcntl isn't clear about how to get seal-related constants

Bug 156231 bugzilla-daemon-590EEB7GvNiWaY/[email protected] 1 participant 2 messages Sep 6, 2016 – Sep 28, 2016 1 message not in the archive Man-pages: manual pages for Linux -- Sections 2, 3, 4, 5, and 7

lore
Share & tools
lore
#0 lore raw

https://bugzilla.kernel.org/show_bug.cgi?id=156231

Bug ID: 156231
Summary: man fcntl isn't clear about how to get seal-related
constants
Product: Documentation
Version: unspecified
Hardware: All
OS: Linux
Status: NEW
Severity: normal
Priority: P1
Component: man-pages
Assignee: documentation_man-pages-ztI5WcYan/[email protected]
Reporter: [email protected]
Regression: No

man fcntl tells you to include unistd.h and fcntl.h - but to get the seal-related constants, you need (it seems) to include linux/fcntl.h.

The need for _GNU_SOURCE (etc.) for other constants is called out clearly enough in the CONFORMING TO section. The directions for the seal-related constants are a bit unclear.

(Perhaps this is just one of those things you're supposed to know, but pages such as shm_open and 2 stat show that being clear about the headers is not without precedent...)

Stack Overflow question:
http://stackoverflow.com/questions/39353442/f-seal-seal-undeclared-even-when-headers-are-included

Thanks,

--Tom

Signature · 6 lines
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

A message that is not in the archive (sent off-list or not yet received): bug-156231-11311-3bo0kxnWaOQUvHkbgXJLS5sdmw4N0Rt+2LY78lusg7I@public.gmane.org/

#2 lore raw

[Bug 156231] man fcntl isn't clear about how to get seal-related constants

https://bugzilla.kernel.org/show_bug.cgi?id=156231

Michael Kerrisk <[email protected]> changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #1 from Michael Kerrisk <[email protected]> --- The problem is that the glibc headers have not yet imported these definitions, so we're currently in "no man's land".

Cheers,

Michael

Signature · 6 lines
You are receiving this mail because:
You are watching the assignee of the bug.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html