Re: Problem with "configure checks for gcc options that clang does not support"

2012-04-24 Thread Michael Stahl
On 24/04/12 12:26, Lubos Lunak wrote: > On Tuesday 24 of April 2012, Tor Lillqvist wrote: >>> But the bug seems to exists only with Clang < 3.1, >> >> The current Apple Clang is 3.1 (tags/Apple/clang-318.0.58) (based on >> LLVM 3.1svn). > > The fix is dated "Tue Mar 13 20:09:56 2012 +". th

Re: Problem with "configure checks for gcc options that clang does not support"

2012-04-24 Thread Lubos Lunak
On Tuesday 24 of April 2012, Tor Lillqvist wrote: > >  That does not quite work, e.g. the message can be translated. > > Ah. > > >  But the bug seems to exists only with Clang < 3.1, > > The current Apple Clang is 3.1 (tags/Apple/clang-318.0.58) (based on > LLVM 3.1svn). The fix is dated "Tue Mar

Re: Problem with "configure checks for gcc options that clang does not support"

2012-04-24 Thread Tor Lillqvist
>  That does not quite work, e.g. the message can be translated. Ah. >  But the bug seems to exists only with Clang < 3.1, The current Apple Clang is 3.1 (tags/Apple/clang-318.0.58) (based on LLVM 3.1svn). --tml ___ LibreOffice mailing list LibreOffic

Re: Problem with "configure checks for gcc options that clang does not support"

2012-04-24 Thread Lubos Lunak
On Monday 23 of April 2012, Tor Lillqvist wrote: > Unfortunately, at least the Apple Clang doesn't generate any > compilation error or *proper* warning for command-line options it > doesn't understand, like -fno-enforce-eh-specs. > > It just prints out clang: warning: argument unused during compila

Problem with "configure checks for gcc options that clang does not support"

2012-04-23 Thread Tor Lillqvist
Unfortunately, at least the Apple Clang doesn't generate any compilation error or *proper* warning for command-line options it doesn't understand, like -fno-enforce-eh-specs. It just prints out clang: warning: argument unused during compilation: '-fno-enforce-eh-specs' to stderr... Even with -Werr