Wireshark-bugs: [Wireshark-bugs] [Bug 5878] gcc unrecognized option during build in OS X
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=5878
Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |jeff.morriss.ws@xxxxxxxxx
--- Comment #1 from Jeff Morriss <jeff.morriss.ws@xxxxxxxxx> 2012-05-23 18:24:56 PDT ---
This:
http://gcc.gnu.org/ml/gcc/2005-12/msg00367.html
says this of the -no-cpp-precomp flag:
> It is only supported by Apple's compiler, not part of the FSF GCC.
> Python is incorrect for using it unconditionally based on the target.
Wireshark's configure.in says:
~~~
darwin*)
#
# It may be called "cc", but it's really a GCC derivative
# with a problematic special precompiler and precompiled
# headers; turn off the special precompiler, as some
# apparently-legal code won't compile with its precompiled
# headers.
#
# On the other hand, if it's called "clang", it's not a
# GCC derivative, and it whines if you pass it
# -no-cpp-precomp.
#
# XXX - is there any version of autoconf we support
# where it uses another way to decide if the compiler
# is GCC or not?
#
if test "x$CC" != "xclang" ; then
CFLAGS="-no-cpp-precomp $CFLAGS"
AC_MSG_RESULT(Apple CC - added -no-cpp-precomp)
else
~~~
I take these to mean that we should only add this flag if we're on darwin and
the compiler is named 'cc' (not 'gcc'). That's easy enough to do, but I'll
await some feedback from those with Macs (or knowledge of them) before making
such a change. (Especially since the MacOS buildbots seem to be using 'gcc'
but don't complain about this command-line argument. Maybe that XXX comment
means the problem is we can't tell the difference between Apple's compiler and
a real GCC?
--
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are watching all bug changes.
