Now that I've calmed down (!) I agree with all Allen's points below. After I installed Xcode 3.1 the remainder of the installation worked flawlessly.
The installation process writes a lot of notes to the console. Most of these are just "unpacking this", "building this" and so on. I did notice at one point, though, a message indicating that I would need to perform the following steps manually after the install completed: sudo port install python_select sudo python_select python25 I ran these steps manually after the MacPorts install finished. Solfege appears to be working fine. I'd say Allen and Rainer have done a great job. Regards, Peter Dann On 31/03/2009, at 11:09 AM, Allen McBride wrote: > Sorry about that. Downloading Xcode 3.1 is definitely the most time- > consuming (though not the most difficult) part of the whole > process. On the bright side, I'm pretty sure those 30 minutes of > installs were not wasted; if they didn't give errors, my > understanding is that those ports didn't require Xcode 3.1 and were > installed correctly. I discovered the new 3.1 requirement in the > same way (by getting an error on a port install). Once I installed > Xcode 3.1, MacPorts just went on with installing the ports that had > failed before, it didn't re-install the old ones, and this hasn't > caused me any trouble so far. I'll update the Solfege wiki to > emphasize MacPorts' Xcode version requirement. > > --Allen > > > > On Mar 30, 2009, at 7:22 PM, Peter Dann wrote: > >> Hi Tom, >> >> I was able to install MacPorts OK on Mac PowerBook Pro running OS X >> Leopard. >> >> However, my attempt to install solfege failed, because I am running >> the version of Xcode (3.0) that shipped with OS X Leopard at the time >> I bought it. The MacPorts install for OS X Leopard requires Xcode >> version 3.1. The MacPorts installation notes imply that you can >> simply >> install the version of Xcode that came with your OS X Leopard >> installation disks. For some lucky users this may be true (perhaps >> Apple now ship Xcode 3.1 with these disks) It is not true for me. >> >> It took MacPorts about 30 minutes of installing various pieces of >> software before it checked that I had an incompatible version of >> Xcode. This strikes me as somewhat dumb. Shouldn't a smart installer >> be able to check the pre-requisites first, before it builds and >> installs 30 minutes worth of software? >> >> My fault, obviously. in part. I should have checked what version of >> Xcode I had installed. I just assumed I had installed the right >> version because it was the one that shipped with OS X. >> >> Looks like I'm going to need to download a 1G (sic) pre-requisite >> just >> to upgrade solfege! >> >> All in all, I found the fink installation process that I previously >> used to install solfege easier to use - though I guess this could >> still work if only users followed the instructions. >> >> Regards, >> >> Peter Dann >> >> >> On 29/03/2009, at 6:16 AM, Tom Cato Amundsen wrote: >> >>> Nice work! >>> People, please post a reply to this message to the list if you have >>> tried the macport, and let us know if it works or not. >>> >>> Tom Cato >>> >>> On Sat, Mar 28, 2009 at 6:40 PM, Allen McBride <[email protected] >>>> wrote: >>>> Hi Tom Cato and everyone, >>>> >>>> With the help of MacPorts project manager Rainer Müller, Solfege >>>> 3.14.0 is now available via MacPorts (http://www.macports.org/). >>>> I'll >>>> work on writing up basic instructions for the wiki soon, explaining >>>> what MacPorts is and where to find instructions for installing and >>>> using it. In the meantime, anyone who already uses MacPorts should >>>> be >>>> able to install Solfege in the usual MacPorts way. If you try it >>>> and >>>> run into trouble, let me know. I think Rainer and I are the only >>>> people who have tested it so far. >>>> >>>> Details: >>>> Rainer wrote a patchfile for default.config, so a Mac user using >>>> MacPorts shouldn't need to mess with Solfege's preferences to get >>>> basic MIDI playback working. So no more "No module named >>>> _solfege_c_midi" error, hopefully. Also, in order to keep things >>>> simple for now, the port does not attempt to install CSound for the >>>> intonation exercises, nor does it attempt to install audio >>>> converters >>>> for lesson file export. Users can still add these on themselves. >>>> >>>> --Allen >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> _______________________________________________ >>>> Solfege-devel mailing list >>>> To UNSUBSCRIBE, email to solfege-devel- >>>> [email protected] >>>> with a subject of "unsubscribe", or visit >>>> https://lists.sourceforge.net/lists/listinfo/solfege-devel >>>> >>> >>> >>> >>> -- >>> Tom Cato Amundsen <[email protected]> http:// >>> www.solfege.org/ >>> GNU Solfege - free ear training http://www.gnu.org/software/ >>> solfege/ >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Solfege-devel mailing list >>> To UNSUBSCRIBE, email to [email protected] >>> with a subject of "unsubscribe", or visit >>> https://lists.sourceforge.net/lists/listinfo/solfege-devel >>> >> >> >> ------------------------------------------------------------------------------ >> _______________________________________________ >> Solfege-devel mailing list >> To UNSUBSCRIBE, email to [email protected] >> with a subject of "unsubscribe", or visit >> https://lists.sourceforge.net/lists/listinfo/solfege-devel > > ------------------------------------------------------------------------------ _______________________________________________ Solfege-devel mailing list To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe", or visit https://lists.sourceforge.net/lists/listinfo/solfege-devel
