I will try the build of boost 1.54 with all the KiCad patches first, then I will try the stock 1.57 later.
> On Nov 19, 2014, at 12:38 PM, Adam Wolf <adamww...@gmail.com> wrote: > > I have not switched to stock boost at this point. > > On Wed, Nov 19, 2014, 11:35 AM Jean-Paul Louis <lou...@yahoo.com> wrote: > Hi Adam, > > I tried homebrew when I started using OS X, but got frustrated and switched > to macports, and never looked back. > I found a page that seems to help a lot for macports users. See below. > When I am done with the migration, I will restart building cicada, and let > you know what method I am using. > Before the upgrade, I was using the method described in your document, with > cmake and make. > I need to modify the build to use a stock boost as described in the list a > little while back. > > Regards, > Jean-Paul > AC9GH > > >> https://trac.macports.org/wiki/Migration >> <https://trac.macports.org/wiki/Migration> >> >> Migrating a MacPorts install to a new major OS version or CPU architecture >> >> A MacPorts installation is designed to work with a particular operating >> system and a particular hardware architecture. Upgrading the operating >> system (e.g., from Mavericks to Yosemite) or migrating to a new machine with >> a different architecture (e.g., from PowerPC to Intel) will generally cause >> problems. The following procedure is designed to prevent such problems. >> >> (The procedure is not necessary after Xcode upgrades unless one of the >> scenarios listed above also applies.) >> >> Migration procedure >> >> Reinstall Xcode. After performing either of these types of system upgrades, >> you will need to update the development tools. If you are upgrading from a >> prior version of OS X, install the latest version of Xcode >> <https://guide.macports.org/#installing.xcode> for your new OS. >> Reinstall MacPorts. After updating the development tools, install the base >> MacPorts system <https://www.macports.org/install.php> for your new >> platform, either from the appropriate pkg or dmg file if already available >> or from source <https://www.macports.org/guide/#installing.macports.source>. >> Update macports.conf. If your macports.conf contains uncommented settings >> for universal_archs or build_arch, you will likely want to update them, >> since unlike earlier OS versions, the compiler on Snow Leopard and later >> will build for x86_64 by default on systems that support it. The default >> values will be fine for almost all users, so unless you know you need >> something different, just comment out these two lines. Several other >> settings in macports.conf have changed their defaults over the years. Take a >> moment to compare each line of your macports.conf with the corresponding >> line in macports.conf.default in the same directory. Unless you know a >> reason why a line your settings file should be different from the defaults, >> adopt the line from the defaults file. >> Reinstall ports. To reinstall your ports: >> Save the list of installed ports: >> port -qv installed > myports.txt >> (optional) Save the list of requested ports: >> port echo requested | cut -d ' ' -f 1 > requested.txt >> Uninstall all installed ports: >> sudo port -f uninstall installed >> Clean any partially-completed builds: >> sudo port clean all >> Download and execute the restore_ports script. (If you installed MacPorts >> from source and used a custom prefix, then you'll need to use the -p option >> when you run restore_ports.tcl; see ./restore_ports.tcl -h.) >> curl -O >> https://svn.macports.org/repository/macports/contrib/restore_ports/restore_ports.tcl >> chmod +x restore_ports.tcl >> sudo ./restore_ports.tcl myports.txt >> (optional) Restore requested status: If you saved the list of requested >> ports, you can now restore the requested flags for your newly installed >> ports to their former states. >> sudo port unsetrequested installed >> < requested.txt xargs sudo port setrequested >> Troubleshooting >> >> Though it is now quite well-tested, the restore_ports script may fail in >> some cases. One known issue is that the script will fail if there are >> conflicting ports in the list. It's possible to have conflicting ports >> installed provided at most one of the conflicting set is active. If the >> script fails for this reason, you can delete one of the conflicting ports >> from myports.txt and then simply run the script again. You may need to do >> this multiple times if there are multiple conflicting ports listed. >> >> In the worst case, you can reinstall your ports manually: >> >> Browse myports.txt and install the ports one by one, remembering to specify >> the appropriate variants: >> sudo port install portname +variant1 +variant2 … >> Note that if you have specified variants which are not the default, you may >> need to install ports in an order other than the alphabetical order recorded >> in myports.txt. You may skip explicitly installing ports that you did not >> request as long as they are not using non-default variants, since they will >> be installed as dependencies of other ports. _______________________________________________ Mailing list: https://launchpad.net/~kicad-developers Post to : kicad-developers@lists.launchpad.net Unsubscribe : https://launchpad.net/~kicad-developers More help : https://help.launchpad.net/ListHelp
