[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Fun with upgrades - not
From: |
David Kastrup |
Subject: |
Re: Fun with upgrades - not |
Date: |
Fri, 08 Jul 2016 14:17:40 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
"Phil Holmes" <address@hidden> writes:
>>> address@hidden:~/lilypond-git/build$ fontforge --version
>>> bash: /usr/local/bin/fontforge: cannot execute binary file: Exec
>>> format error
>>
>> What does
>>
>> file /usr/local/bin/fontforge
>>
>> state? This sounds like you are trying to run a 64bit executable on a
>> 32bit kernel, or a 32bit executable on a system unequipped to do so
>> (missing essential libraries and loaders). Or even have a complete
>> mismatch of architecture.
>
> Looks right:
>
> address@hidden:~/lilypond-git$ file /usr/local/bin/fontforge
> /usr/local/bin/fontforge: ELF 64-bit LSB executable, x86-64, version 1
> (SYSV), dynamically linked (uses shared libs), for GNU/Linux 2.6.15,
> BuildID[sha1]=1c01d759ac10c3f83d000f8e3d36cbea63f909e5, not stripped
>
> It's 32 bit OS. Any idea how to replace it with a 32 bit version?
See Alexander's reply: /usr/local/ is the normal directory for
installing stuff compiled by the user. You probably needed a newer
version of fontforge than the system-distributed one at one time and
compiled and installed it there yourself.
So you'll need to clean out the fontforge installation in /usr/local/ in
order to let the system version take over. How to best do that depends
on how it got installed there in the first place.
--
David Kastrup
Re: Fun with upgrades - not, Federico Bruni, 2016/07/08
Re: Fun with upgrades - not, Alexander Kobel, 2016/07/08