Re: ld: can't write output file for architecture ppc
On Mon, 18 Mar 2024, raf via macports-users wrote: > I've been told that macports needs to be selfupdated at least annually. > If it's been too long between selfupdates, it can fail (It did for me > once on 10.6.8). You might need to reinstall macports instead of > selfupdate. Annually? Yikes; I run it weekly... -- Dave
Re: ld: can't write output file for architecture ppc
raf wrote: I've been told that macports needs to be selfupdated at least annually. If it's been too long between selfupdates, it can fail (It did for me once on 10.6.8). You might need to reinstall macports instead of selfupdate. To any expoerts out there, does that sound helpful? I wouldn't uninstall just yet, and definitely not without making a backup first, as it will remove the possibility of easily restoring the old versions. When you upgrade, MacPorts will only deactivate the old versions of ports (unless specifically told to immediately uninstall them). So you should be able to activate the older versions to get back to the state you were in previously. It should be pretty obvious which is which based on the timestamps in 'port -v installed'. If you want to try to go ahead with upgrading, I would first 'port deactivate active' and then 'port install' (not upgrade) the ports you want to use. That will still use anything you already have installed if possible, saving some build time, and will avoid any issues with ancient variants, replaced ports and such. If that still fails, you still have the option of reactivating the old versions. - Josh
Re: ld: can't write output file for architecture ppc
On Sun, Mar 17, 2024 at 02:50:37PM +0100, Riccardo Mottola via macports-users wrote: > Hi Andreas, > > > Andreas Falkenhahn wrote: > > ld: can't write output file for architecture ppc > > > > gcc-mp-6 itself apparently is still working. I have compared the object > > files generated by it from before and after the attempted MacPorts update > > and they're identical but ld seems broken. Is there any way I can get ld > > back up and running? > > > > No, I don't have a backup of my old MacPorts installation, another > > mistake:( > > > > It's really annoying. I really could've sensed that updating a 2017 > > MacPorts installation on a 20 year old system nobody besides me is still > > using would never go through but still I tried... silly, silly me!! > > It is a big jump in updates, but on the other side you are not the only one > uses. I am using 10.5 on PPC and Intel and other MacPorts users are on PPC > or other legacy systems, so there is still good effort updating things. > > I have GCC working on my G4. I updated dozen of packages last week. > > I have a couple of "leftovers" I want to report and tackle, some are generic > to 10.5, some are specific to ppc / gcc, because on Intel the preferred > compiler is clang. > > > > > Any idea how I can get that fixed? > > I would have a look at the linker, binutils and similar. > Are you on G3/G4 or G5 ? > > does gcc fail when used outside MacPorts or does it always fail? > > Since I have a working gcc, you should be able too. > > Riccardo I've been told that macports needs to be selfupdated at least annually. If it's been too long between selfupdates, it can fail (It did for me once on 10.6.8). You might need to reinstall macports instead of selfupdate. To any expoerts out there, does that sound helpful? cheers, raf
Re: ld: can't write output file for architecture ppc
Hi Andreas, Andreas Falkenhahn wrote: ld: can't write output file for architecture ppc gcc-mp-6 itself apparently is still working. I have compared the object files generated by it from before and after the attempted MacPorts update and they're identical but ld seems broken. Is there any way I can get ld back up and running? No, I don't have a backup of my old MacPorts installation, another mistake:( It's really annoying. I really could've sensed that updating a 2017 MacPorts installation on a 20 year old system nobody besides me is still using would never go through but still I tried... silly, silly me!! It is a big jump in updates, but on the other side you are not the only one uses. I am using 10.5 on PPC and Intel and other MacPorts users are on PPC or other legacy systems, so there is still good effort updating things. I have GCC working on my G4. I updated dozen of packages last week. I have a couple of "leftovers" I want to report and tackle, some are generic to 10.5, some are specific to ppc / gcc, because on Intel the preferred compiler is clang. Any idea how I can get that fixed? I would have a look at the linker, binutils and similar. Are you on G3/G4 or G5 ? does gcc fail when used outside MacPorts or does it always fail? Since I have a working gcc, you should be able too. Riccardo
ld: can't write output file for architecture ppc
Hi, for several years I've been successfully using gcc-mp-6 on a PPC Mac running OS X 10.5. I installed MacPorts and gcc-mp-6 back in 2017 and haven't updated anything concerning MacPorts since. Now I wanted to install a new MacPorts package and in order to install the package it also forced me to update MacPorts. In hindsight that was a BIG, BIG mistake because of course it aborted somewhere in the middle of the update process and now it looks like my installation is f*** up because whenever I try to link something I now get the error: ld: can't write output file for architecture ppc gcc-mp-6 itself apparently is still working. I have compared the object files generated by it from before and after the attempted MacPorts update and they're identical but ld seems broken. Is there any way I can get ld back up and running? No, I don't have a backup of my old MacPorts installation, another mistake :( It's really annoying. I really could've sensed that updating a 2017 MacPorts installation on a 20 year old system nobody besides me is still using would never go through but still I tried... silly, silly me!! Any idea how I can get that fixed? -- Best regards, Andreas Falkenhahn mailto:andr...@falkenhahn.com
