[MacPorts] #31002: wireshark 1.6.0 build uses large amount of RAM (possible compiler bug?)

MacPorts noreply at macports.org
Sun Aug 28 06:13:57 PDT 2011


#31002: wireshark 1.6.0 build uses large amount of RAM (possible compiler bug?)
------------------------------+---------------------------------------------
 Reporter:  cal@…             |       Owner:  opendarwin.org@…          
     Type:  defect            |      Status:  new                       
 Priority:  Normal            |   Milestone:                            
Component:  ports             |     Version:  2.0.1                     
 Keywords:  lion              |        Port:  wireshark                 
------------------------------+---------------------------------------------
 Hi.

 Compiling wireshark 1.6.0 on Lion with llvm-gcc-4.2 (default Xcode 4.1
 compiler) needs an unusually large amount of RAM when compiling a specific
 file (unfortunately I don't know which, htop output wasn't long enough,
 but I guess that should be easy to find out when not building parallel and
 looking at the build output). Compiling that file never finished (waited
 about 15 minutes when the process was near 10GB of virtual memory).

 Installing with configure.compiler=clang works albeit throwing a lot of
 warnings. I used +gnutls+ipv6+libgcrypt+pcre+universal, although I have
 observed the same problem without +gnutls+libgcrypt before.

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


More information about the macports-tickets mailing list