Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
On 14 September 2017 at 06:30, Ian Wadham wrote: > I am in a right royal mess with some KDE 4 applications and libraries from > MacPorts > on which I depend. After a failed "sudo port upgrade outdated" run all my > KDE 4 apps > give OSX popup messages like "kmymoney cannot be opened because of a problem" > and they wil not start. The most serious (for me) is KMyMoney, which holds > all my > finances and investments, and it is time for me to do annual accounting and > tax. > > I am using OSX 10.7.5 Lion and MacPorts 2.4.1. > > It was some time since I had done a port upgrade outdated, maybe a year or > more. That's generally a long time period. > However a "sudo port selfupdate" showed that I was already at macports 2.4.1. > I then > ran and saved lists of requested and outdated ports and uninstalled a few > ports I no > longer need. Then I started "sudo port upgrade outdated". > > The terminal output ended with multiple repetititions of: > Warning: reinplace /include/s@\(utils\.h\)@src/\1@g didn't change anything in > /opt/local... This is totally harmless. It could be fixed, but it won't affect you. > Followed by: > ---> Configuring akonadi > Error: akonadi does not support your selected MacPorts C++ runtime. libc++ > must be selected and C++-based ports built against it. As Ken suggested, you could try to open that Portfile (check "port dir akonadi") and replace PortGroup cxx11 1.0 with PortGroup cxx11 1.1 and hope that it will succeed. > 1. Do I need to do any cleanup of the failed run before doing anything else? > If so, > what command(s) should I use? Yes, generally, whenever a port fails to build it's a good idea to run "port clean ", then fix something and run "sudo port -v install " again. That will compile to the end. (If you need to manually patch something little in the sources that you discover while running the build, it's better if you don't clean it, else you need to provide a "permanent patch", but that's a different story.) > 2. I had a local ports tree that I no longer use. I have commented out the > reference > to it in sources.conf but do I need to re-run portindex? No. > Or would that have been > taken care of when I ran "sudo port selfupdate"? I have not found any > way to > re-index and include just the standard ports. You only need to run portindex to generate an index of a new or updated ports tree. If you remove a local tree, you only need to remove the reference. Portindex is generated at the location of the ports tree. > 3. Can I revert to earlier versions of apps and libraries (which could at > least be used > to keep my accountant happy)? If so, what commands should I use? There > are > scores, maybe hundreds, of ports to be reactivated and there are probably > lots > that are old but still active, because the upgrade run never got to them. You can run "port installed" to check which ports you have installed. Then you run sudo port activate portname@version for all the ports in question. That is, assuming you didn't delete any of them. If you know the point in time when all the ports worked you can also do a git checkout of the tree, switch to an old commit (from approximately the time when everything worked) and use that one as the main ports tree. Then you will get all the old versions back. > 4. If I stay with Lion, I understand that I have to uninstall everything, > make some > adjustments to macports.conf and then re-build from source and continue to > do so into the future. You also need to keep in mind that the number of people (developers in particular) testing the changes on Lion is converging to zero. On Lion you have an option to either use the method mentioned by Ken (cxx11 1.1 portgroup) or go for libc++ installation (reinstall all packages), but any of those options will require manually dealing with compilation issues every now and then, so you should better not be afraid to fix Portfiles. An additional problem is that if you are looking for KDE, it requires Qt which is a moving target which is constantly dropping support for older OSes. So unless someone tested it for you and removed the problems, you might run into getting a too new version of KDE that's no longer supported on 10.7 and you might need to adapt the dependencies manually. You need to be aware that if you go for libc++, at the time being you'll have to compile everything from source which is particularly painful for all the compilers and Qt. Depending on your hardware (I assume it's not the latest one if you still have 10.7 installed) it might literally take days before you have done compiling/debugging/starting the next round/... even if you won't have to intervene much. > OTOH I could go down to the Apple shop and get them to upgrade me to > Sierra > and then I could re-install MacPorts apps from binaries but I would also > have to > upgrade other non-Apple so
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi, I understand what these messages mean and I have read the Macports Wiki pages referred to, but I am uncertain what to do next. 1. Do I need to do any cleanup of the failed run before doing anything else? If so, what command(s) should I use? 2. I had a local ports tree that I no longer use. I have commented out the reference to it in sources.conf but do I need to re-run portindex? Or would that have been taken care of when I ran "sudo port selfupdate"? I have not found any way to re-index and include just the standard ports. 3. Can I revert to earlier versions of apps and libraries (which could at least be used to keep my accountant happy)? If so, what commands should I use? There are scores, maybe hundreds, of ports to be reactivated and there are probably lots that are old but still active, because the upgrade run never got to them. 4. If I stay with Lion, I understand that I have to uninstall everything, make some adjustments to macports.conf and then re-build from source and continue to do so into the future. OTOH I could go down to the Apple shop and get them to upgrade me to Sierra and then I could re-install MacPorts apps from binaries but I would also have to upgrade other non-Apple software I depend on a lot every day, mainly Firefox and LibreOffice. Either approach could take days (elapsed) and many hours of computer time. Which way would be best for me to go? Go with 4. Update to Sierra, it will save you most trouble in the long run. No need at all to go to a store to get it done though, just do it yourself Download the updater from the App Store and follow the instructions. Firefox and LibreOffice might also need updating, if you haven't kept them up to date, but both will work fine in the newer OS. cheers Chris
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
On 14 September 2017 at 10:10, Chris Jones wrote: > > Update to Sierra, it will save you most trouble in the long run. > No need at all to go to a store to get it done though, just do it > yourself Download the updater from the App Store and follow the > instructions. Firefox and LibreOffice might also need updating, if you > haven't kept them up to date, but both will work fine in the newer OS. Just to avoid any confusion from my long complex email: this *exactly* is my opinion as well. Going back in time and activate ports that already worked for you might be the fastest solution in the short run that could be done in 15-60 minutes (if you know what you are doing) without taking other risks of potentially hitting other issues on the new os. But once the super-hurry is over, going to Sierra would greatly greatly reduce most of your headaches in the long run. The upgrade should be pretty fast and painless anyway. Any OSes below 10.9 are a bit of a headache and besides of security risks & lack of software it only makes sense to use them if you know exactly what you are doing and if you can help yourself when you hit problems. High Sierra is also on the way, but it will bring its own set of headaches until the majority of ports are fixed, so probably not suggested to install it yet if you cannot live with broken ports. Mojca
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi Ian, I also jumped from Lion to Sierra recently but my old Macbook pro with a HD slowed down a lot and it took a couple of days to be functional again (you have to reinstall XCode, XQuartz,…). OTOH, note that Firefox is not maintained for Lion since end of 2016 I believe. Not very secure. Finally my MBP died and I moved to a more recent one with a SSD + 16 Gb ram and speed has resumed to normal… cheers, Laurent > Le 14 sept. 2017 à 10:10, Chris Jones a écrit : > > Hi, > > >> I understand what these messages mean and I have read the Macports Wiki pages >> referred to, but I am uncertain what to do next. >> 1. Do I need to do any cleanup of the failed run before doing anything else? >> If so, >> what command(s) should I use? >> 2. I had a local ports tree that I no longer use. I have commented out the >> reference >> to it in sources.conf but do I need to re-run portindex? Or would that >> have been >> taken care of when I ran "sudo port selfupdate"? I have not found any >> way to >> re-index and include just the standard ports. >> 3. Can I revert to earlier versions of apps and libraries (which could at >> least be used >> to keep my accountant happy)? If so, what commands should I use? There >> are >> scores, maybe hundreds, of ports to be reactivated and there are >> probably lots >> that are old but still active, because the upgrade run never got to them. >> 4. If I stay with Lion, I understand that I have to uninstall everything, >> make some >> adjustments to macports.conf and then re-build from source and continue >> to >> do so into the future. >> OTOH I could go down to the Apple shop and get them to upgrade me to >> Sierra >> and then I could re-install MacPorts apps from binaries but I would also >> have to >> upgrade other non-Apple software I depend on a lot every day, mainly >> Firefox >> and LibreOffice. >> Either approach could take days (elapsed) and many hours of computer >> time. >> Which way would be best for me to go? > > Go with 4. Update to Sierra, it will save you most trouble in the long run. > No need at all to go to a store to get it done though, just do it > yourself Download the updater from the App Store and follow the > instructions. Firefox and LibreOffice might also need updating, if you > haven't kept them up to date, but both will work fine in the newer OS. > > cheers Chris "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi, On 14/09/17 09:34, Mojca Miklavec wrote: On 14 September 2017 at 10:10, Chris Jones wrote: Update to Sierra, it will save you most trouble in the long run. No need at all to go to a store to get it done though, just do it yourself Download the updater from the App Store and follow the instructions. Firefox and LibreOffice might also need updating, if you haven't kept them up to date, but both will work fine in the newer OS. Just to avoid any confusion from my long complex email: this *exactly* is my opinion as well. If/when you do update the OS, you should of course follow the instructions at https://trac.macports.org/wiki/Migration to migrate MP. Going back in time and activate ports that already worked for you might be the fastest solution in the short run that could be done in 15-60 minutes (if you know what you are doing) without taking other risks of potentially hitting other issues on the new os. Another option would be to restore the MP prefix (/opt/local normally) from a backup. Assuming you have backups of course... If not adding this to your regular maintenance to do list should be the first thing you do. But once the super-hurry is over, going to Sierra would greatly greatly reduce most of your headaches in the long run. The upgrade should be pretty fast and painless anyway. Any OSes below 10.9 are a bit of a headache and besides of security risks & lack of software it only makes sense to use them if you know exactly what you are doing and if you can help yourself when you hit problems. High Sierra is also on the way, but it will bring its own set of headaches until the majority of ports are fixed, so probably not suggested to install it yet if you cannot live with broken ports. OT, but whether or not the mac OS10.13 is smooth or not depends a bit on what you update. If we put aside the APFS update for the moment, I expect it to be rather painless... I actually have tested the beta in a VM and it worked fine, I was able to build all the ports I normally install without issue.. The APFS update, for SSD macs, is another thing. This might well cause a number of issues. For instance last I heard Xquartz (xorg-server in MP) does not work with APFS. No idea if this is fixed (I understand it was an Apple issue). I rely on this so I will be holding off the update, or at least allowing the APFS conversion, until I hear news on this.. I suspect there will be other ports that will need updating to work with the new filesystem... Chris Mojca
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
> On Sep 14, 2017, at 01:48, Chris Jones wrote: > > Hi, > > On 14/09/17 09:34, Mojca Miklavec wrote: >> On 14 September 2017 at 10:10, Chris Jones wrote: >>> >>> Update to Sierra, it will save you most trouble in the long run. >>> No need at all to go to a store to get it done though, just do it >>> yourself Download the updater from the App Store and follow the >>> instructions. Firefox and LibreOffice might also need updating, if you >>> haven't kept them up to date, but both will work fine in the newer OS. >> Just to avoid any confusion from my long complex email: this *exactly* >> is my opinion as well. > > If/when you do update the OS, you should of course follow the instructions at > > https://trac.macports.org/wiki/Migration > > to migrate MP. > >> Going back in time and activate ports that already worked for you >> might be the fastest solution in the short run that could be done in >> 15-60 minutes (if you know what you are doing) without taking other >> risks of potentially hitting other issues on the new os. > > Another option would be to restore the MP prefix (/opt/local normally) from a > backup. Assuming you have backups of course... If not adding this to your > regular maintenance to do list should be the first thing you do. > >> But once the super-hurry is over, going to Sierra would greatly >> greatly reduce most of your headaches in the long run. The upgrade >> should be pretty fast and painless anyway. >> Any OSes below 10.9 are a bit of a headache and besides of security >> risks & lack of software it only makes sense to use them if you know >> exactly what you are doing and if you can help yourself when you hit >> problems. >> High Sierra is also on the way, but it will bring its own set of >> headaches until the majority of ports are fixed, so probably not >> suggested to install it yet if you cannot live with broken ports. > > OT, but whether or not the mac OS10.13 is smooth or not depends a bit on what > you update. If we put aside the APFS update for the moment, I expect it to be > rather painless... I actually have tested the beta in a VM and it worked > fine, I was able to build all the ports I normally install without issue.. > > The APFS update, for SSD macs, is another thing. This might well cause a > number of issues. For instance last I heard Xquartz (xorg-server in MP) does > not work with APFS. No idea if this is fixed That was addressed in a beta quite a while ago (beta 5?). > (I understand it was an Apple issue). I rely on this so I will be holding off > the update, or at least allowing the APFS conversion, until I hear news on > this.. I suspect there will be other ports that will need updating to work > with the new filesystem... > > Chris > >> Mojca
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
On 14 Sep 2017, at 06:30, Ian Wadham wrote: > The most serious (for me) is KMyMoney, which holds all my finances and > investments, and it is time for me to do annual accounting and tax. In case you have Time Machine or a clone, just restore /opt/local/ and /Applications/MacPorts/.
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi everybody, Thank you so very much for all the helpful advice and suggestions. I live in Australia, so it is TV veg-out time and nearly bedtime. I will work through all your replies in detail in the morning. On 14/09/2017, at 7:57 PM, db wrote: > On 14 Sep 2017, at 06:30, Ian Wadham wrote: >> The most serious (for me) is KMyMoney, which holds all my finances and >> investments, and it is time for me to do annual accounting and tax. > > In case you have Time Machine or a clone, just restore /opt/local/ and > /Applications/MacPorts/. Heh, heh! Someone else suggested that and it was also one of the first things I thought of. But guess what. I have TimeMachine, but my settings exclude backing up /opt/local and several other build/object-code areas, on the basis that they are large and the wherewithal to re-create them is easily available elsewhere. in source-code directories, MacPorts servers, etc. Well, it is the first time in six years I have been caught out… :-( Mind you, I should have upgraded my OSX long ago and none of this would have happened… :-( Cheers, Ian W.
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi Chris, On 14/09/2017, at 6:10 PM, Chris Jones wrote: >> I understand what these messages mean and I have read the Macports Wiki pages >> referred to, but I am uncertain what to do next. >> 1. Do I need to do any cleanup of the failed run before doing anything else? >> If so, >> what command(s) should I use? >> 2. I had a local ports tree that I no longer use. I have commented out the >> reference >> to it in sources.conf but do I need to re-run portindex? Or would that >> have been >> taken care of when I ran "sudo port selfupdate"? I have not found any >> way to >> re-index and include just the standard ports. >> 3. Can I revert to earlier versions of apps and libraries (which could at >> least be used >> to keep my accountant happy)? If so, what commands should I use? There >> are >> scores, maybe hundreds, of ports to be reactivated and there are >> probably lots >> that are old but still active, because the upgrade run never got to them. >> 4. If I stay with Lion, I understand that I have to uninstall everything, >> make some >> adjustments to macports.conf and then re-build from source and continue >> to >> do so into the future. >> OTOH I could go down to the Apple shop and get them to upgrade me to >> Sierra >> and then I could re-install MacPorts apps from binaries but I would also >> have to >> upgrade other non-Apple software I depend on a lot every day, mainly >> Firefox >> and LibreOffice. >> Either approach could take days (elapsed) and many hours of computer >> time. >> Which way would be best for me to go? > > Go with 4. Update to Sierra, it will save you most trouble in the long run. > No need at all to go to a store to get it done though, just do it > yourself Download the updater from the App Store and follow the > instructions. Firefox and LibreOffice might also need updating, if you > haven't kept them up to date, but both will work fine in the newer OS. > > cheers Chris If I go to Sierra, will I lose the Apple apps in Lion that play (and burn) DVDs? I notice that new MacBook Pros with Sierra usually do not have a CD/DVD drive… Of course Sierra will still have iTunes, but will it still play CDs? I only ever use iTunes for that. Cheers, Ian W.
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
No problem. When I moved to Sierra with my old MBP, it still read and engraved CDs/DVDs and you can buy an external CD player on USB connexion, which implies that Sierra can still deal with it! Ciao, Laurent > Le 14 sept. 2017 à 13:40, Ian Wadham a écrit : > > Hi Chris, > > On 14/09/2017, at 6:10 PM, Chris Jones wrote: >>> I understand what these messages mean and I have read the Macports Wiki >>> pages >>> referred to, but I am uncertain what to do next. >>> 1. Do I need to do any cleanup of the failed run before doing anything >>> else? If so, >>> what command(s) should I use? >>> 2. I had a local ports tree that I no longer use. I have commented out the >>> reference >>>to it in sources.conf but do I need to re-run portindex? Or would that >>> have been >>>taken care of when I ran "sudo port selfupdate"? I have not found any >>> way to >>>re-index and include just the standard ports. >>> 3. Can I revert to earlier versions of apps and libraries (which could at >>> least be used >>>to keep my accountant happy)? If so, what commands should I use? There >>> are >>>scores, maybe hundreds, of ports to be reactivated and there are >>> probably lots >>>that are old but still active, because the upgrade run never got to them. >>> 4. If I stay with Lion, I understand that I have to uninstall everything, >>> make some >>>adjustments to macports.conf and then re-build from source and continue >>> to >>>do so into the future. >>>OTOH I could go down to the Apple shop and get them to upgrade me to >>> Sierra >>>and then I could re-install MacPorts apps from binaries but I would also >>> have to >>>upgrade other non-Apple software I depend on a lot every day, mainly >>> Firefox >>>and LibreOffice. >>>Either approach could take days (elapsed) and many hours of computer >>> time. >>>Which way would be best for me to go? >> >> Go with 4. Update to Sierra, it will save you most trouble in the long run. >> No need at all to go to a store to get it done though, just do it >> yourself Download the updater from the App Store and follow the >> instructions. Firefox and LibreOffice might also need updating, if you >> haven't kept them up to date, but both will work fine in the newer OS. >> >> cheers Chris > > If I go to Sierra, will I lose the Apple apps in Lion that play (and burn) > DVDs? I notice that new MacBook Pros with Sierra usually do not have > a CD/DVD drive… Of course Sierra will still have iTunes, but will it > still play CDs? I only ever use iTunes for that. > > Cheers, Ian W. "S'il n'y a pas de solution, c'est qu'il n'y a pas de problème" (devise Shadok)
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
Hi, On 14/09/17 10:49, Jeremy Huddleston Sequoia wrote: On Sep 14, 2017, at 01:48, Chris Jones wrote: Hi, On 14/09/17 09:34, Mojca Miklavec wrote: On 14 September 2017 at 10:10, Chris Jones wrote: Update to Sierra, it will save you most trouble in the long run. No need at all to go to a store to get it done though, just do it yourself Download the updater from the App Store and follow the instructions. Firefox and LibreOffice might also need updating, if you haven't kept them up to date, but both will work fine in the newer OS. Just to avoid any confusion from my long complex email: this *exactly* is my opinion as well. If/when you do update the OS, you should of course follow the instructions at https://trac.macports.org/wiki/Migration to migrate MP. Going back in time and activate ports that already worked for you might be the fastest solution in the short run that could be done in 15-60 minutes (if you know what you are doing) without taking other risks of potentially hitting other issues on the new os. Another option would be to restore the MP prefix (/opt/local normally) from a backup. Assuming you have backups of course... If not adding this to your regular maintenance to do list should be the first thing you do. But once the super-hurry is over, going to Sierra would greatly greatly reduce most of your headaches in the long run. The upgrade should be pretty fast and painless anyway. Any OSes below 10.9 are a bit of a headache and besides of security risks & lack of software it only makes sense to use them if you know exactly what you are doing and if you can help yourself when you hit problems. High Sierra is also on the way, but it will bring its own set of headaches until the majority of ports are fixed, so probably not suggested to install it yet if you cannot live with broken ports. OT, but whether or not the mac OS10.13 is smooth or not depends a bit on what you update. If we put aside the APFS update for the moment, I expect it to be rather painless... I actually have tested the beta in a VM and it worked fine, I was able to build all the ports I normally install without issue.. The APFS update, for SSD macs, is another thing. This might well cause a number of issues. For instance last I heard Xquartz (xorg-server in MP) does not work with APFS. No idea if this is fixed That was addressed in a beta quite a while ago (beta 5?). Good to hear, many thanks ... I was unable to test this myself as I have only tested macOS10.13 either on an external USB drive, or in a VM, and in each case it was not possible (DiskUtility did not allow it) to update the partition to APFS. cheers Chris (I understand it was an Apple issue). I rely on this so I will be holding off the update, or at least allowing the APFS conversion, until I hear news on this.. I suspect there will be other ports that will need updating to work with the new filesystem... Chris Mojca
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
On 14 Sep 2017, at 13:25, Ian Wadham wrote: > On 14/09/2017, at 7:57 PM, db wrote: >> In case you have Time Machine or a clone, just restore /opt/local/ and >> /Applications/MacPorts/. > Heh, heh! Someone else suggested that and it was also one of the first > things I > thought of. But guess what. I have TimeMachine, but my settings exclude > backing up /opt/local and several other build/object-code areas, on the basis > that > they are large and the wherewithal to re-create them is easily available > elsewhere. > in source-code directories, MacPorts servers, etc. I didn't intend to re-post a suggestion, but that one missed the second path (see man porthier). I also had my prefix excluded from Time Machine until I encountered some bug in vim that went for weeks unresolved. Not worth the time and you can always delete older backups to make room in your disk. From then on I try to port upgrade right after a TM backup. This is just pragmatic. You could use git branch as others proposed, but I presume you'll end up with a full set of older dependencies for some ports. You might want to try your most used tools first in a VM with 10.12 or 10.13. Also, in addition to the migration page, check https://trac.macports.org/wiki/SierraProblems.
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
> If you know the point in time when all the ports worked you can also > do a git checkout of the tree, switch to an old commit (from > approximately the time when everything worked) and use that one as the > main ports tree. Then you will get all the old versions back. This is a very useful activity to understand if you haven't updated for a long time. In essence, it will give the ports tree you had a year ago. Then you can reinstall your ports from that date, get going again, and then do things in a more controlled fashion. I just like the older OSes -- this MacBookPro I'm on now has Sierra installed, but I prefer SnowLeopard. Apple must hate me :> Ken
Re: In a mess with libc++ libstdc++ and OSX 10.7.5 Lion
With regard to the question of "Will DVD's work?", the answer is VLC and/or MakeMKV. VLC has so far worked on any DVD I've tossed at it, even ones that DVDPlayer.app did not like because of region mismatch. And MakeMKV is designed to extract the movies from DVD's even when the DVD is using more than just CSS scrambled sectors (deliberately mis-authored with the cells not properly sequenced ... apparently DVD's include a control language that can work around this? The same thing that lets Dragon's Lair type games play can play customized playback orders.)
