/usr/local/bin/lynx: Bad CPU type in executable
macportsusers-20171215 at billmail.scconsult.com
Sat Dec 21 04:25:44 UTC 2019
On 20 Dec 2019, at 23:07, Michael Newman via macports-users wrote:
> MacPorts Version: 2.6.2
> macOS 10.15.2
> I installed lynx today and received the error message:
> /usr/local/bin/lynx: Bad CPU type in executable
That's a bad place for MacPorts to be installing lynx or anything else.
MacPorts installs under /opt/local by default and if you force it to
install in /usr/local you are asking for trouble.
Is it possible that your /usr/local/bin/lynx is a relic of some ancient
time and a different machine? I ask this because I had that problem once
upon a time. Before switching to MacPorts, I built a bunch of stuff by
hand and had a /usr/local that started life on a Cube and ended its
useful life on a G5 iMac before being moved to a Core Duo iMac, where it
ultimately went bad because binaries built for a PowerPC G4 on 10.2
simply will not run on a Core Duo on 10.6. The result of trying to do so
(or to run 32-bit Intel code on 10.15.x) is the error message "Bad CPU
type in executable"
> Is there anything I can do about this?
This by itself may fix your problewm:
You may also need to add /opt/local/bin to your PATH environment
bill at scconsult.com or billcole at apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Not For Hire (currently)
More information about the macports-users