Opened 14 years ago
Closed 13 years ago
#29485 closed defect (worksforme)
gcc44 failed to complete when doing "sudo port upgrade outdated"
Reported by: | dgh@… | Owned by: | mww@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.9.2 |
Keywords: | Cc: | ||
Port: | gcc44 |
Description
OSX 10.6.5. Performed selfupdate and the upgrade outdated commands.
The gcc44 portfile has Revision 78606. After letting it run overnight, I did a quick defect search and found defect #24541. This closed ticket said the gcc configuration process was confused by a symlink in /usr/include.
I looked in my /usr/include directory and found many symlinks associated with tcl/tk (attached is list of symlink files).
After moving these files to a subdirectory, gcc44 promptly completed with no errors.
I didnt save the log file from the build that took forever, but Im sure I could recreate it.
I dont think this is a defect in the gcc44 portfile, but I do think this could be a defect in the gcc configuration process, following up on irrelevant symlinks.
The symlinks were made months ago. I dont remember what install I was performing that created the symlinks. At the time I was interest in various python modules so I could have installed something from the macpython site that made these links.
This anomaly deserves higher visibility. Maybe the resolution is warning messages from the portfile, maybe its a bugreport to the gcc owners, maybe its just a hint in the documentation that this symlinks will confuse some ports.
Attachments (1)
Change History (5)
Changed 14 years ago by dgh@…
Attachment: | symlinks.txt added |
---|
comment:1 Changed 14 years ago by jmroot (Joshua Root)
Owner: | changed from macports-tickets@… to mww@… |
---|---|
Port: | gcc44 added |
Type: | submission → defect |
Please remember to fill in the Port field and cc the maintainer.
comment:2 Changed 14 years ago by jmroot (Joshua Root)
#24541 doesn't have anything to do with Tcl/Tk headers. You'll need to show what exactly the error you got was.
comment:3 Changed 13 years ago by dgh@…
Replying to dgh@…:
I'm a little chagrined to say I cant reproduce it.
I moved the symlinks back in place, uninstalled gcc44 (with -f) and installed it.
It ran to completion.
Please close this ticket. I'll be more careful next time and investigate further. I promise!
comment:4 Changed 13 years ago by jmroot (Joshua Root)
Resolution: | → worksforme |
---|---|
Status: | new → closed |
ls of the symbolic links that interfered with the gcc44 install.