Opened 16 years ago
Closed 14 years ago
#16618 closed defect (wontfix)
Building gcc43 on Leopard Intel locks computer
| Reported by: | jwhowse4 | Owned by: | mww@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | Cc: | ryandesign (Ryan Carsten Schmidt), oshima@… | |
| Port: | gcc43 |
Description
I have a new Mac Pro with Intel Xeon processors running Leopard 10.5.5 and Xcode 3.1.1. When I try to compile gcc43, my computer locks up completely, apparently while trying to run ranlib to create the x86-64 version of libgfortran.a. I am sorry that I can not provide the exact state, but since the machine locks I can not save any state information. I can provide two other pieces of data. First, fink successfully builds the x86-64 version of libgfortran.a. Second, when I add the flag --disable-multilib to the configure.args line in the macports Portfile, gcc43 builds successfully. Has anyone else encountered a problem like this??? Thanks, James
Change History (11)
comment:1 follow-up: 2 Changed 16 years ago by mf2k (Frank Schima)
| Owner: | changed from macports-tickets@… to mww@… |
|---|---|
| Port: | gcc43 added |
comment:2 Changed 16 years ago by jwhowse4
Replying to macsforever2000@…:
Assigning to maintainer.
I do not see this problem and I have the same setup as you. Do you have fink installed on the machine at the same time as MacPorts? That is known to cause problems.
I do use both, but when I am installing macports software my environment is configured in such a way that fink is invisible, meaning I remove all environment variables which reference any part of fink. Also I have been using both in this manner for about 18 months on a MacBook Pro running Tiger 10.4.11 without seeing any problems. In addition,
comment:3 follow-up: 4 Changed 16 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | ryandesign@… added |
|---|
@jwhowse4: "In addition" what? :)
Removing environment variables may not be sufficient to hide Fink from software installed with MacPorts. It would be better to rename Fink's /sw directory to something else any time you want to use MacPorts or any software installed using MacPorts. Since that's clearly inconvenient, it might be more convenient to use MacPorts (or Fink) exclusively and remove the other. If MacPorts doesn't have some software you need, please file port request tickets.
comment:4 Changed 16 years ago by kevin.squire+macports@…
I can confirm that this problem is an interaction with fink. I had the same issue--I would describe it as the disk drive spinning down, and any program needing access to the disk becoming unresponsive. OTOH, anything not needing to access the disk still worked fine.
Following the advise of ryandesign, I renamed my fink /sw directory, and gcc43 installed fine.
It still seems strange to me that such an interaction would be as severe as preventing access to the disk...
Kevin
comment:5 Changed 16 years ago by jwhowse4
I tested the conjecture that this is a fink interaction by reinstalling my operating system, installing MacPorts as the first and only piece of software, and then installing gcc43 under MacPorts. My computer still freezes completely sometimes. There are several other people at my company having similar issues and we have been in touch with Apple. The current hypothesis is that they is a subtle problem with Leopard when run on the Mac Pro hardware, because we have not seen problems on any other hardware.
comment:6 Changed 16 years ago by oshima@…
Sorry about adding comment for this (probably) non-MacPorts-specific problem.
I have exactly the same problem on a Mac Pro, OS X 10.5.6 that the disk drive spins down and the computer locks completely, while ranlib is being run in building gcc43 in MacPorts. I don't have Fink installed either. In fact gcc43 is not the only software that triggers this problem while building, but here is the only place I could find after having googled around hard for this problem. Did any one of you find a solution for this problem?
comment:9 follow-up: 10 Changed 14 years ago by ryandesign (Ryan Carsten Schmidt)
Is anybody still seeing this problem?
I could see this being an OS bug, or OS corruption, or hardware failure, but have a hard time seeing a bug in MacPorts causing a computer to lock up completely.
comment:10 Changed 14 years ago by oshima@…
Replying to ryandesign@…:
No, I no longer see the problem after upgrading OS X to 10.6. Thanks for the heads up.
comment:11 Changed 14 years ago by jmroot (Joshua Root)
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
Doesn't seem like there's anything we can do about this one.
Assigning to maintainer.
I do not see this problem and I have the same setup as you. Do you have fink installed on the machine at the same time as MacPorts? That is known to cause problems.