![]() ![]() At least I have the new working port of boost for myself now. However, I consider my task completed, when I uploaded the updated patch to the MacPorts ticket. So the ABI instability is really an issue, and I understand now why boost was stuck at the old version for such a long time. After that, everything went on smoothly.Īgainst all my hopes, I found that I had to rebuild mkvtoolnix yet again. It was actually due to trivial code changes in Boost, but I still had to check all the rejections, manually apply the changes, and generate a new patch file. Most of these MacPorts-specific patch files could be applied without any problems, but one of them failed. Then came the more painful process of fixing the patch files under devel/boost/files (the ‘patch’ I mentioned a moment ago actually contained patches for these patch files). When I could see the new version 1.61.0 from port info boost, I kicked off the build with port upgrade boost again. I changed first Portfile, which contained the version information and file checksums. I had to port uninstall it and then port install it again (rebuilding it).Īfter I had some confidence, I began to change the port files. The procedure turned out quite smooth, though mkvtoolnix, the only installed port that depended on boost on my laptop, failed to run after the upgrade. I simply applied the patch, ran portindex again, and went ahead to port upgrade boost. The patch was still good to me, as I had now a good example. Here are direct links for the latest versions of macOS: macOS 12 Monterey: MacPorts-2.8. It turned out that people tried to update boost half a year ago for Boost 1.60, but they found there were failing ports and the ABI was incompatible with 1.59. Download the latest MacPorts-2.8.1-.pkg installer from the releases on GitHub. Now MacPorts should find ports first in my local ports directory and then the system default. It needs to be rerun every time a Portfile is changed. Run the portindex command under that directory.‘ file:///Users/yongwei/Programming/MacPorts’ in my case) to /opt/local/etc/macports/nf, above the default rsync URL. ![]() Add the URL of the local ports directory (e.g.One then needs to tell MacPorts to look for ports in that directory. So I checked out only the boost directory into ~/Programming/MacPorts/devel. In my case, The boost files are under devel/boost. The first thing one needs to do is check out the port files from the MacPorts Subversion repository. This article will document the procedure how it works. With the help from Mr Michael Dickens and Google, I have a working port of Boost 1.61.0 now. ![]() So this morning I subscribed to the MacPorts mailing list and posted the question about the outdated version problem. After I built Microsoft’s cpprestsdk last night-I managed to make it find and use the MacPorts Boost libraries-I feel more urged to change the situation. So I had two sets of Boost libraries on my hard drive, which made things. When I wrote about Boost.Coroutine2, I found I had to install the latest Boost version 1.61.0. You can, however, selectively upgrade ports if you want to delay other upgrades until later.
0 Comments
Leave a Reply. |