(sorry, hit Ctrl-Enter instead of Enter....) On Sun, 2008-09-14 at 17:07 +0200, Patrick Ale wrote: > - When configure checks if the compiler understands -std=9x > -no-strict-aliasing, cc throws a warning about illegal flags but > produces an executable binary. Configure takes this as the compiler > understanding the -std=9x and -fno-strict-aliasing flags. On compile > stage these warnings result in a non zero exit, which is interpreted > as failure.
Hmmm... it sounds like JH_ADD_CFLAG is wrong, then. If it causes an error during compilation but not in configure, then the macro in configure is doing something differently. If you fix the macro, I'm sure it will be accepted upstream. Laca
