From b75e038615d51cb62c200e336e59202519db8cae Mon Sep 17 00:00:00 2001 From: Thomas Schwinge Date: Sun, 13 May 2012 22:36:45 +0800 Subject: IRC. --- open_issues/glibc.mdwn | 29 +++++++++++++++++++++++++++++ 1 file changed, 29 insertions(+) (limited to 'open_issues/glibc.mdwn') diff --git a/open_issues/glibc.mdwn b/open_issues/glibc.mdwn index 6c52cc7f..1ce47560 100644 --- a/open_issues/glibc.mdwn +++ b/open_issues/glibc.mdwn @@ -189,6 +189,35 @@ Last reviewed up to the [[Git mirror's d40c5d54cb551acba4ef1617464760c5b3d41a14 `open_by_handle_at`, `process_vm_readv`, `process_vm_writev`, `sendmmsg`, `setns`, `sync_file_range` + * `chflags` + + IRC, OFTC, #debian-hurd, 2012-04-27: + + Does anyone have any idea why int main(void) { return + chflags(); } will compile with gcc but not with g++ ? It says + that "chflags" was not declared in this scope. + I get the same error on FreeBSD, but including sys/stat.h + makes it work + Can't find a solution on Hurd though :/ + the Hurd doesn't have chflags + apparently linux neither + what does it do? + change flags :) + Are you sure the Hurd does not have chflags ? Because gcc + does not complain + there is no chflags function in /usr/include + but what flags does it change? + According to the FreeBSD manpage, it can set flags such as + UF_NODUMP, UF_IMMUTABLE etc. + Hum, there is actually a chflags() definition + but no declaration + so actually chflags is supported, but the declaration was + forgotten + probably because since linux doens't have it, it has never + been a problem up to now + so I'd say ignore the error for now, we'll add the + declaration + * `getcontext`/`setcontext` Needed for [[gccgo]]. -- cgit v1.2.3