lilypond-user
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: lilypond-2.19.80-1.linux-64.sh


From: David Kastrup
Subject: Re: lilypond-2.19.80-1.linux-64.sh
Date: Tue, 31 Oct 2017 23:12:07 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.0.50 (gnu/linux)

[Public Cc since you apparently only mailed me with your answer]

Blöchl Bernhard <address@hidden> writes:

> Am 31.10.2017 22:29, schrieb David Kastrup:
>> Blöchl Bernhard <address@hidden> writes:
>>
>>> cannot install  lilypond-2.19.80-1.linux-64.sh
>>>
>>>  *-cpu:0
>>>        Beschreibung: CPU
>>>        Produkt: Intel(R) Pentium(R) 3556U @ 1.70GHz
>>>        Hersteller: Intel Corp.
>>>        Physische ID: 4
>>>        Bus-Informationen: address@hidden
>>>        Version: 6.5.1
>>>        Seriennummer: 0004-0651-0000-0000-0000-0000
>>>        Steckplatz: U3E1
>>>        Größe: 1201MHz
>>>        Kapazität: 1700MHz
>>>        Breite: 64 bits
>>>        Takt: 100MHz
>>>
>>> I have installed the 64 bit-Version of linux mint 18.2 mate "Sonya"
>>
>> Sounds very much like you didn't.
>>
>> What does
>>
>>     arch
>>
>> reply?
>
>
>
> Aspire-ES1-571 ~ $ arch
> i686

That is a 32-bit system.  A 64-bit system would reply x86_64 instead.

> Intel Product Specifications for Intel® Pentium® Processor 3556U
> (
> https://ark.intel.com/products/76621/Intel-Pentium-Processor-3556U-2M-Cache-1_70-GHz
> )tells:
> ...
> Intel® 64 ‡ Yes
> Instruction Set 64-bit
> ...

That just means that your processor would be capable of running a 64-bit
system.  Not that it is currently running one.

>>> Aspire-ES1-571 ~/lilypond/usr/share $ lilypond -v
>>> /home/bb/lilypond/usr/bin/lilypond: 1:
>>> /home/bb/lilypond/usr/bin/lilypond: Syntax error: ")" unexpected
>>
>> That's typical for calling 64bit executables on a 32bit system.
>
> Indeed it is strange!

Note that this can also mean that you are running inside of 32-bit
container or VM.  Either way the level you are trying to install/run
LilyPond under is a 32-bit system.

-- 
David Kastrup



reply via email to

[Prev in Thread] Current Thread [Next in Thread]