Axoloti software installation (ubuntu 32bit)

nampuapx · 2015-08-26 14:57:29 UTC

Hallo! I want install axoloti software on ubuntu 14.04 and i.m get next:

kolino@kolino-ThinkPad-Z61m:/discD/mydo/!distr/!axoloti$ sudo dpkg -i axoloti-linux-1.0.3.deb
[sudo] password for kolino: 
dpkg: error processing archive axoloti-linux-1.0.3.deb (--install):
 package architecture (amd64) does not match the system architecture (i386)

....
I think - i must build software from source. How this do?

Sputnki · 2015-08-26 15:24:51 UTC

You don't have to build anything, just follow the instructions you find here https://sebiik.github.io/community.axoloti.com.backup/t/installing-on-linux/56 , maybe you have to change filenames, but everything is there

raboof · 2015-08-26 19:49:01 UTC

Hello,

The error message you're seeing means the Debian package claims it is built for 64-bits operating systems, while you are running a 32-bits one.

I'm not sure the binary package actually contains any 32-bits-specific stuff. You might want to try the .tar.gz package.

If you indeed must build from source, check the instructions under 'Developer Installation' at https://sebiik.github.io/community.axoloti.com.backup/t/installing-on-linux/56.

Let us know how things go and whether you run into any further problems!

nampuapx · 2015-08-27 08:27:20 UTC

Yes, I tried it...

kolino@kolino-ThinkPad-Z61m:/discD/mydo/!distr/!axoloti/axoloti-1.0.3/platform_linux$ build.sh
build.sh: command not found

something I'm doing wrong

raboof · 2015-08-27 08:37:43 UTC

To run build.sh, you should type "./build.sh" (as '.' is not on the PATH by default on linux)

nampuapx · 2015-08-27 10:00:02 UTC

thank! it is right!
now he wants to lib32z1 lib32ncurses5 lib32bz2-1.0
the same problem as you have

thetechnobear · 2015-08-27 12:26:05 UTC

@raboof pointed to a possible way to solve this here :

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install zlib1g:i386 libncurses5:i386 libbz2-1.0:i386

can you try this, (typing it in) and let me know if this works, if it does then I will add this to the user guide, and also add it to the ./build.sh

obviously I only want to do this, once I know someone has tested and knows it works

nampuapx · 2015-08-28 10:50:45 UTC

I tried it. the result is not received. nothing changed. (as I understand it, the system is said - these packages are already installed)

libbz2-1.0 is already the newest version.
libncurses5 is already the newest version.
zlib1g is already the newest version.

but when I'm writing build.sh goes:

E: Unable to locate package lib32z1
E: Unable to locate package lib32ncurses5
E: Unable to locate package lib32bz2-1.0

thetechnobear · 2015-08-28 13:15:28 UTC

edit build.sh
and change:

sudo apt-get install -y libtool libudev-dev automake autoconf ant curl lib32z1 lib32ncurses5 lib32bz2-1.0

to

sudo apt-get install -y libtool libudev-dev automake autoconf ant curl

if you have them installed, perhaps it will just work...

and will anyway be enlightening to if you still get errors

nampuapx · 2015-08-29 13:22:11 UTC

Yes, I read here, too https://sebiik.github.io/community.axoloti.com.backup/t/lib32bz2-1-0-no-longer-available-on-debian/333/4
And I commented out the library ...
Now, when I run ./Axoloti.sh, I get:

kako@kako-VGN-P19VRN-Q:/windows/mydo/distr/axoloti/axoloti-1.0.3$ ./Axoloti.sh
Axoloti.jar does not exist.

thetechnobear · 2015-08-29 15:58:18 UTC

did you run build.sh after commenting out, and did it run to completion?
was there an error?

anyway, to build the jar, just type

ant

(in the same directory as Axoloti.sh)

also make sure you have the JDK installed, as per the instructions... OpenJDK Java 1.7 will do.

mcpepe · 2016-01-07 19:06:56 UTC

I am getting this same error, with Axoloti 1.0.6

I am a complete newcomer to Ubuntu (I have just installed) so I dont know much about Linux. I have installed Ubuntu 14.04 LTS. It is the 32 bit version for my old 2006 Intel white Imac

It is posible to install it in a 32 bit version or it needs a 64 bit OS?

johannes · 2016-01-07 22:21:35 UTC

I'm not building 32 bit ubuntu packages. Why did you select 32bit over 64bit?

Building from source is likely to work on 32bit with relatively little trouble.

github.com

axoloti/axoloti/blob/master/doc/compiling%20from%20source%20on%20linux.html

<html><body>
<h1>Compiling from source on Linux</h1>
        Assuming Ubunut Linux. Other Distributions may need minor changes.
        <h2>Download</h2>

        
        <h3>From GIT</h3>
        Open a terminal and enter:<p>
        <code>
            $> <b>git clone https://github.com/axoloti/axoloti.git</b><br>
        </code>       
        
        <h2>Install</h2>
        
        Root privileges are required to add a udev rule to grant access to Axoloti Core on USB.
        
        open a terminal and enter:<p>
        <code>
            $> <b>cd axoloti</b><br>
            $> <b>cd platform_linux</b><br>

This file has been truncated. show original

mcpepe · 2016-01-07 22:30:30 UTC

I have choosen the 32bit Ubuntu because my 2006 Intel IMac is not able to run the 64bit version. I tried.

This IMac newest's OSX version I can install is 10.6.8, and Axoloti needs 10.7 minimum, so I am not able to install Axoloti using OSX.

johannes · 2016-01-07 22:48:11 UTC

OK
Nothing in Axoloti really depends on 64bitness, it's just that 32bit is not popular anymore.

fuzzySi · 2016-03-04 23:47:01 UTC

I'd certainly vote for a compiled 32 bit linux version - running ./build.sh gives an error on 32 bit Linux Mint:
Cannot handle dist: LinuxMint
Genuinely the first time this 10 year old computer hasn't been able to run something, which is a shame if there's no specifically 64 bit code. I wonder if it should be clearer that it only runs on certain Linux distros?

thetechnobear · 2016-03-05 00:13:48 UTC

just alter the build.sh , its not that difficult... something any linux guy should be able to handle.
especially as it appears linuxmint is debian based.

then send a pull request via github with changes, so that the next linuxmint user has it 'out of the box'... thats kind of the point of open source.

fuzzySi · 2016-03-05 16:53:21 UTC

OK thanks, I'll have a go. Not used github yet but I'll document here what I've done.

Editing build.sh to allow mint - to edit:
sudo nano build.sh

add "|LinuxMint" so it looks like this - Ubuntu|Debian|LinuxMint - in a couple of places in the file
(look in /etc/lsb-release and copy whatever comes after DISTRIB_ID=)

sudo dpkg --add-architecture i386
sudo apt-get update
sudo apt-get install zlib1g:i386 libncurses5:i386 libbz2-1.0:i386

this gives the "latest version already" output as above.

looks like you have to remove references to those files in both lines of build.sh - so edit build.sh again, just stick a comment # in front of the file names after curl

This starts to compile but breaks:

-do-compile:
[mkdir] Created dir: /home/doris/Software/axoloti/build/empty
[mkdir] Created dir: /home/doris/Software/axoloti/build/generated-sources/ap-source-output
[javac] Compiling 396 source files to /home/doris/Software/axoloti/build/classes
[javac] warning: [options] bootstrap class path not set in conjunction with -source 1.6
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:3: error: unclosed string literal
[javac] public final static String AXOLOTI_VERSION = "fatal: Not a git repository (or any parent up to mount point /home/doris)
[javac] ^
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:4: error: ';' expected
[javac] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).";
[javac] ^
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:4: error: ')' expected
[javac] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).";
[javac] ^
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:4: error: illegal start of type
[javac] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).";
[javac] ^
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:4: error: expected
[javac] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).";
[javac] ^
[javac] /home/doris/Software/axoloti/src/main/java/axoloti/Version.java:4: error: unclosed string literal
[javac] Stopping at filesystem boundary (GIT_DISCOVERY_ACROSS_FILESYSTEM not set).";
[javac] ^
[javac] 6 errors
[javac] 1 warning

BUILD FAILED
/home/doris/Software/axoloti/nbproject/build-impl.xml:911: The following error occurred while executing this line:
/home/doris/Software/axoloti/nbproject/build-impl.xml:261: Compile failed; see the compiler error output for details.

fuzzySi · 2016-03-06 00:41:30 UTC

I finally got it working, but not quite sure how - I ended up compiling it on 2 different machines both running linux mint 17, and copied one version of the folder to my main linux which was giving compile errors. The patches and objects folders were both empty, but I had also managed to get the normal version working on my son's 64bit linux mint, and copied the relevant files from there. The GUI still won't let me access library files, but it's working so I can edit patches. Sorry not to be able to give accurate guidance on how to get it working - it was by accident not design.
More laborious than I was hoping - maybe 4 hours to get this going - but it's a beautiful program when you get there. I still love my nord micromodular but this looks to be much more hackable, though my main need currently is just a drum sampler - I'm sure this will take it in interesting directions.

thetechnobear · 2016-03-06 01:02:02 UTC

did you clone the git directory to get the initial version of the software?
(you should do this, rather than just download the zip from the github server)

these are a sub repository... so once the clone is done,
you will need to do

 git submodule update --init --recursive

(as detailed in the read me file)

Id then advise changing directories into axoloti-contrib and axolotl-factory (each in turn)
and type

 git checkout master

yeah if your not used to building software from source, it can be a bit time consuming initially (for most software products) .... its not ideal, but given the plethora of linux platforms around its not practical to add them all, even package managers vary so much across them ... then 32 and 64 bit variants, a big task to do all combos