[MacPorts] #32386: wireshark @1.6.4_0: Build problem with llvm-gcc-4.2

[MacPorts]

#32386: wireshark @1.6.4_0: Build problem with llvm-gcc-4.2
---------------------------------+------------------------------------------
 Reporter:  raimue@…             |       Owner:  opendarwin.org@…          
     Type:  defect               |      Status:  new                       
 Priority:  Normal               |   Milestone:                            
Component:  ports                |     Version:  2.0.3                     
 Keywords:                       |        Port:  wireshark                 
---------------------------------+------------------------------------------
 wireshark @1.6.4_0 forces the use of llvm-gcc-4.2 instead of clang. I
 experienced a build problem with llvm-gcc-4.2, where the compiler seemed
 to enter and endless loop and started allocating more and more memory.

 {{{
 $ sudo port -v build wireshark build.jobs=1
 ...
 libtool: compile:  ccache /Developer/usr/bin/llvm-gcc-4.2 -DHAVE_CONFIG_H
 -I. -I. -I../.. -I./../.. -I./.. -I/opt/local/include -I/opt/local/include
 -I/opt/local/include -I/opt/local/include -I/opt/local/include
 -DPLUGIN_DIR=\"/opt/local/lib/wireshark/plugins/1.6.4\" -no-cpp-precomp
 "-D_U_=__attribute__((unused))" -pipe -O2 -arch x86_64 -Wall -W -Wextra
 -Wdeclaration-after-statement -Wendif-labels -Wpointer-arith -Wno-pointer-
 sign -Wcast-align -Wformat-security -I/opt/local/include -D_REENTRANT
 -I/opt/local/include/gtk-2.0 -I/opt/local/lib/gtk-2.0/include
 -I/opt/local/include/atk-1.0 -I/opt/local/include/cairo
 -I/opt/local/include/gdk-pixbuf-2.0 -I/opt/local/include/pango-1.0
 -I/opt/local/include/gio-unix-2.0/ -I/opt/local/include
 -I/opt/local/include/glib-2.0 -I/opt/local/lib/glib-2.0/include
 -I/opt/local/include/pixman-1 -I/opt/local/include/freetype2
 -I/opt/local/include/libpng14 -I/opt/local/include -I/opt/local/include
 -MT libdissectors_la-packet-rtmpt.lo -MD -MP -MF .deps/libdissectors_la-
 packet-rtmpt.Tpo -c packet-rtmpt.c  -fno-common -DPIC -o .libs
 /libdissectors_la-packet-rtmpt.o
 }}}

 It just hangs here and I see a cc1 process consuming lots of memory. I
 retried the build with clang instead, which works fine for me.

 What was the reason to force the use of llvm-gcc-4.2? I suggest to reverse
 this change.

-- 
Ticket URL: <https://trac.macports.org/ticket/32386>
MacPorts <http://www.macports.org/>
Ports system for Mac OS