On 20.03.2024 at 00:00 Ryan Schmidt wrote:
> As Josh explained, run:
> port -v installed
> If I wanted to downgrade from sqlite3 @3.45.2_0 which I installed
> in March back to sqlite3 @3.45.1_1 which I installed in February, I would run:
> sudo port activate sqlite3 @3.45.1_1
> If you reactiva
On Mar 19, 2024, at 10:21, Andreas Falkenhahn wrote:
>
>> 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 previous
Macports-users wrote:
> Are you on G3/G4 or G5 ?
G5.
> I would have a look at the linker, binutils and similar.
But where should I look? When I examine /opt/local/bin it's pretty
messy because 50% of the files have a timestamp of 2017 and the
other half has a 2024 timestamp so it really looks l
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
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
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 compa
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
lso 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 o
