Re: [PATCH 5/5] Add dummy return 0 to Xnest Xephyr io error handler for Sun compilers

2011-12-03 Thread Mikhail Gusarov
Twas brillig at 15:08:49 02.12.2011 UTC-08 when alan.coopersm...@oracle.com did gyre and gimble: AC Uses Studio-specific pragma to avoid causing gcc to warn about having AC a redundant prototype for the exit() function. AC Signed-off-by: Alan Coopersmith alan.coopersm...@oracle.com

Re: [PATCH 5/5] Add dummy return 0 to Xnest Xephyr io error handler for Sun compilers

2011-12-03 Thread walter harms
Hi, perhaps you can call it DUMMY_RETURN or so ? Other compilers may have the same idea. Otherwise ... will gcc complain ? If not something like: return 0; /* make SUNPRO C happy */ would sufficent. re, wh Am 02.12.2011 19:48, schrieb Alan Coopersmith: Required in order to build with

[PATCH 5/5] Add dummy return 0 to Xnest Xephyr io error handler for Sun compilers

2011-12-02 Thread Alan Coopersmith
Required in order to build with Studio cc now that xorg-macros is setting -errwarn=E_FUNC_HAS_NO_RETURN_STMT since it doesn't recognize that the noreturn attribute makes it pointless. Otherwise compiler exits with errors: Display.c, line 65: Function has no return statement : x_io_error_handler