[MacPorts] #13430: Macports 1.5-10.5 fails to install on a brand new Mac
#13430: Macports 1.5-10.5 fails to install on a brand new Mac --------------------------------+------------------------------------------- Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: MacPorts 1.5 Component: base | Version: 1.5.0 Keywords: | --------------------------------+------------------------------------------- Fresh installation of Mac OS X 10.5.1, transferred over my /usr/local from my old iBook G4 and tried to install MacPorts, which failed at the "selfupdate" stage as follows. MacPorts should be able to cope with me having something in /usr/local it doesn't like. -- Ticket URL: <http://trac.macports.org/projects/macports/ticket/13430> MacPorts </projects/macports> Ports system for Mac OS
#13430: Macports 1.5-10.5 fails to install on a brand new Mac - readline ---------------------------------+------------------------------------------ Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: MacPorts 1.5 Component: base | Version: 1.5.0 Resolution: | Keywords: readline ---------------------------------+------------------------------------------ Changes (by afb@macports.org): * keywords: => readline * summary: Macports 1.5-10.5 fails to install on a brand new Mac => Macports 1.5-10.5 fails to install on a brand new Mac - readline Comment: The error is due to the incompatible version of readline installed in /usr/local. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13430#comment:1> MacPorts </projects/macports> Ports system for Mac OS
#13430: Macports 1.5-10.5 fails to install on a brand new Mac - readline ---------------------------------+------------------------------------------ Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: MacPorts 1.5 Component: base | Version: 1.5.0 Resolution: | Keywords: readline ---------------------------------+------------------------------------------ Comment (by slivnik@tomaz.name): Yes of course. That version of readline is required by other software installed in our /usr/local partition. There are many other libraries on our /usr/local partition which are likely to be incompatible with MacPorts. This is standard setup - to put local libraries in /usr/local. MacPorts should be able to handle that; if not, I suggest it is broken. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13430#comment:2> MacPorts </projects/macports> Ports system for Mac OS
#13430: Macports 1.5-10.5 fails to install on a brand new Mac - readline ---------------------------------+------------------------------------------ Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: MacPorts 1.5 Component: base | Version: 1.5.0 Resolution: | Keywords: readline ---------------------------------+------------------------------------------ Comment (by markd@macports.org): MacPorts has already been fixed in HEAD to not compile readline support in by default. When 1.6 comes out (within a few weeks) the change will get rolled into the binary installer. For now you'll need to work around it by renaming /usr/local while installing MP binary, or install MP from source by checking it out from SVN and installing it that way. http://trac.macosforge.org/projects/macports/wiki/GetMacPortsSource -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13430#comment:4> MacPorts </projects/macports> Ports system for Mac OS
#13430: Macports 1.5-10.5 fails to install on a brand new Mac - readline ---------------------------------+------------------------------------------ Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: new Priority: High | Milestone: MacPorts 1.5 Component: base | Version: 1.5.0 Resolution: | Keywords: readline ---------------------------------+------------------------------------------ Comment (by markd@macports.org): << I have no objection to MacPorts being compiled with readline support It has been turned off by default because it is only used in MP interactive mode -a seldom used option. So your non-objection is mute. If you want to know the reasons why readline causes so much trouble for MP, ask the MP developer list or search the list archives. But I think you are simply wrong about how gcc searches for stuff. We turned it off because of all the "oh man it's so easy to avoid /usr/../readline problems" assertions over time; yet actually doing it goes way beyond MP (gcc issues I think) and I don't believe anyone ever came up with a way that would work. But as I said, if you want to argue for the ease of a hypothetical solution, look at the macports-dev archives first and bring the discussion to the list because this has all been discussed before at length. But as I said, it has been turned off and probably few (if any) will miss MP interactive mode. -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13430#comment:6> MacPorts </projects/macports> Ports system for Mac OS
#13430: Macports 1.5-10.5 fails to install on a brand new Mac - readline ---------------------------------+------------------------------------------ Reporter: slivnik@tomaz.name | Owner: macports-dev@lists.macosforge.org Type: defect | Status: closed Priority: Normal | Milestone: MacPorts base bugs Component: base | Version: 1.5.0 Resolution: fixed | Keywords: readline ---------------------------------+------------------------------------------ Changes (by jmpp@macports.org): * priority: High => Normal * status: new => closed * resolution: => fixed * milestone: MacPorts 1.5 => MacPorts base bugs Comment: Will be a non-issue once MacPorts 1.6.0 is out, very soon now! -jmpp -- Ticket URL: <http://trac.macosforge.org/projects/macports/ticket/13430#comment:7> MacPorts </projects/macports> Ports system for Mac OS
participants (1)
-
MacPorts