On 04-03-2014 20:26:28 +0100, Stefan Manegold wrote:
thanks. that's what I wanted to know, i.e., this is not only not gcc, but also different from the clang 3.3 that's available on Linux. Apparently, the latter (still?) supports -pthread while the Apple one does no(t| longer).
No, it just became more strict. It is warning that -pthread doesn't do anything during compilation phase. You can argue this is a clang bug, since -pthread is a compiler switch that says: "do whatever you need to do to get compilation of code against pthread working". In the Darwin case (and also Linux) it doesn't have to do anything.
which doesn't support GCC-only flags. Can we some how update our configure script or something to deal with this in a more elegant way than having to set "export CFLAGS..." each time?
sure. See e.g. what we do already do for clang, icc, and certain (old) versions of gcc. But I propose to check carefully and understand why configure itself or our checks in our configure.ag does not (yet) detect that Apple clang 5.0 does not support -pthread (the way it is currently used).
Again, it does support that flag. You just can't compile with --enable-strict. I suggest you change the configure trickery to disable warning about unused flags for Clang 5. €0.02 Fabian