Just thought I’d mention this really isn’t true, as long as you have installed the proper 32 bit compatibility libraries. I’m currently running Renoise just fine on a 64 bit Ubuntu with no troubles. You just need to remember to install ia32-libs or whatever equivalent exists in your distro.
Oh, and BTW, a big fat “thank you” to all people involved in this port, I love it!
I’m the responsible for the “32bit environment only” statement, because I’m the only one in the Linux test team having a 64bit CPU. I would like to know how you have managed to run Renoise under a 64bit system.
did you simply install ia32 libs, or did you also have to create a chroot environment? if the second case is true, then I think the statement is still true: after all, creating a chroot is nothing more than installing a 32bit environment into a 64bit one.
Just took a look at this again, if its possible to distribute 64bit binaries as well, and I guess thats nothing I can offer for now. Why?
the Renoise backend is not yet ready to be compiled for 64bit. There is not THAT much work left, but this involves a lot of testing and finetuning, also for the other platforms where we sooner or later want to have 64bit binaries. Thats nothing I want to start in a beta cycle, as this can easily result in a huge chaos.
providing 2 builds for Linux (actually 2 new - demos and regged versions) means more overhead for us. Even if the releases are automated, the testing is not (we dont release any build that we dont have at least quickly tested), thus we are happy about any overhead that can be avoided
I even have not yet tested and verified how well GCC cross compiles on Linux - if this works at all in practice. Building the 64bit and 32bit executables on two different machines or VMs means again a lot of overhead for us. Has anyone some experiences with cross-compiling for x86-64 on 32bit systems?
So, in summary: 64builds builds will come, also for Windows and Mac OS, but definitely NOT for this release (1.9.1).
This is very nice to hear. Please let me know if you need any more testers
As for cross compiling, GCC has quite good support for this, but the only way I’ve tried this myself is compiling for 32 bit systems on a 64 bit GCC, where this can be achieved by using the -m32 flag (gcc -m32 hello.c -o hello, for example). This requires the standard stuff, proper headers, proper 32 bit development libs installed. I don’t know if this method will yield a binary that is identical to one a 32 bit GCC would produce, but the resulting binary does work on all 32 bit CPUs you want it to, as decided by the -march flag.
It also seems there’s a -m64 flag on 32 bit GCC’s which would work the other way, but I’ve never tried this myself.
does anyone which libs should i install on fedora 10??
there’s no such a thing like ia32-libs and they told me that fedora supports a multilib system but i won’t install what i don’t really need. the answer could go in the FAQs too tough.