#33469 closed defect (worksforme)
llvm-3.0 @3.0_2: Build hangs
| Reported by: | larryv (Lawrence Velázquez) | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.4 |
| Keywords: | Cc: | jeremyhu (Jeremy Huddleston Sequoia) | |
| Port: | llvm-3.0 |
Description
While trying to build llvm-3.0, one clang process seems to get stuck and start using up gigabytes of RAM. I say "stuck" because the build did not finish after an hour (at which point I killed it).
In contrast, the build was well-behaved and finished in 30 minutes when I used configure.compiler=macports-llvm-gcc-4.2. (I can't try configure.compiler=llvm-gcc-4.2, since Xcode 4.3 lacks it.)
OS X 10.7.3 (11D50b), Xcode 4.3 (4E109), MacPorts 2.0.4.
Change History (4)
comment:1 Changed 13 years ago by jeremyhu (Jeremy Huddleston Sequoia)
| Resolution: | → worksforme |
|---|---|
| Status: | new → closed |
comment:2 Changed 13 years ago by jeremyhu (Jeremy Huddleston Sequoia)
comment:3 Changed 12 years ago by andre.david@…
I just hit this brickwall: ARMDisassembler gobbles up 4 GB of memory while compiling. I'm running OS X 10.8 on 8 GB of RAM and the first time I went through this, it brought the system down (menu bar crashed, dock crashed, etc).
Is there no way to add a warning that you should close all applications? It would have saved me one hour of work at least.
comment:4 Changed 12 years ago by jeremyhu (Jeremy Huddleston Sequoia)
You shouldn't have seen crashes. Those crashes are not related to this.
No log attached. Closing assuming it's taking a long time with ARMDisassembler.cpp ... that's a known issue. You just need to be more patient.