Re: CLANG versus GCC question: compiling non-c99 code with CLANG (clang dumps error)

2012-09-24 Thread Dimitry Andric
On 2012-09-24 13:45, O. Hartmann wrote: ... here it is: win.c:796:50: error: non-void function 'lux_freedata' should return a value [-Wreturn-type] if ( current->win.data == (lux_data *)NULL ) return; ^ Some time ago, the clang developers

Re: CLANG versus GCC question: compiling non-c99 code with CLANG (clang dumps error)

2012-09-24 Thread O. Hartmann
Am 09/24/12 11:52, schrieb Dimitry Andric: > On 2012-09-24 11:36, O. Hartmann wrote: >> I have a problem and I guess there is a simple solution - at least, I >> hope. >> >> I try to compile a "in spe" port which contains some C code that is >> definitely Kernighan & Ritchie standard like: >> >> --

Re: CLANG versus GCC question: compiling non-c99 code with CLANG (clang dumps error)

2012-09-24 Thread Dimitry Andric
On 2012-09-24 11:36, O. Hartmann wrote: I have a problem and I guess there is a simple solution - at least, I hope. I try to compile a "in spe" port which contains some C code that is definitely Kernighan & Ritchie standard like: -- my_func(win) Window win; { [...] if ( current-

CLANG versus GCC question: compiling non-c99 code with CLANG (clang dumps error)

2012-09-24 Thread O. Hartmann
Hello, I have a problem and I guess there is a simple solution - at least, I hope. I try to compile a "in spe" port which contains some C code that is definitely Kernighan & Ritchie standard like: -- my_func(win) Window win; { [...] if ( current->win.data == (lux_data *)NULL ) re