14.04 and other compile errors

[Tim Janik]

Hey Stefan,

I've been investigating more compile errors of Rapicorn (and Beast) with Ubuntu distributions, intermediate summary:
* Recent Rapicorn and Beast build fine on Ubuntu 15.04 64bit (my development machine).
* On Ubuntu 14.04, Rapicorn can be built with your aida.cc fix, a bool array fix in factory.cc and simply downgrading the cython dependency from 0.20.2 to 0.20.1.
* For 14.04 32bit, Rapicorn is buggy, I've fixed some size_t issues locally, will push them soon.
* Beast does *not* build with g++-4.8 from 14.04, seems that compiler cannot handle the template stuff I needed for undo, here's a post explaining why that was quite involved: https://testbit.eu/a-day-of-templates/
** I doubt this can be easily fixed, this might be the turning point where we *have* to upgrade the dependency to g++-4.9...
* Rapicorn does *not* build on Ubuntu-15.10 64bit which ships g++-5.2.1, it currently runs into a union member assertion because sizeof (std::string) is now 32byte instead of 8. I have yet to fix that and investigate further.

I've managed to beef up my dockerfile scripting here, which is how I can test these different distributions.
Running a dockerized Beast does work here through a X11 unix socket and including sound now (but no MIDI so far).

--
Yours sincerely,
Tim Janik

https://testbit.eu/timj/
Free software author and speaker.

[Stefan Westerfeld]

Hi!

On Sun, Oct 04, 2015 at 02:10:58AM +0200, Tim Janik wrote:
> I've been investigating more compile errors of Rapicorn (and Beast) with Ubuntu distributions, intermediate summary:
> * Recent Rapicorn and Beast build fine on Ubuntu 15.04 64bit (my development machine).
> * On Ubuntu 14.04, Rapicorn can be built with your aida.cc fix, a bool array fix in factory.cc and simply downgrading the cython dependency from 0.20.2 to 0.20.1.
> * For 14.04 32bit, Rapicorn is buggy, I've fixed some size_t issues locally, will push them soon.
> * Beast does *not* build with g++-4.8 from 14.04, seems that compiler cannot handle the template stuff I needed for undo, here's a post explaining why that was quite involved: https://testbit.eu/a-day-of-templates/
> ** I doubt this can be easily fixed, this might be the turning point where we *have* to upgrade the dependency to g++-4.9...

I think it's acceptable to upgrade the compiler dependency to g++-4.9. This
will save the trouble of developing a workaround for the undo usecase (a
somewhat tricky piece of code). I tried a few easy things but failed. In any
case I build beast now on Ubuntu-15.04 which has g++-4.9.

Also if you think of Ubuntu LTS versions, the next one is Ubuntu-16.04 LTS.
This is not too far in the future (half a year), so users which only use LTS
Ubuntu will not have to wait too long until their compiler is good enough
(again) to build beast.

> * Rapicorn does *not* build on Ubuntu-15.10 64bit which ships g++-5.2.1, it currently runs into a union member assertion because sizeof (std::string) is now 32byte instead of 8. I have yet to fix that and investigate further.
>
> I've managed to beef up my dockerfile scripting here, which is how I can test these different distributions.
> Running a dockerized Beast does work here through a X11 unix socket and including sound now (but no MIDI so far).

Cu... Stefan
--
Stefan Westerfeld, http://space.twc.de/~stefan

[Tim Janik]

On 09.10.2015 21:29, Stefan Westerfeld wrote:
> Hi!
>
> On Sun, Oct 04, 2015 at 02:10:58AM +0200, Tim Janik wrote:
>> I've been investigating more compile errors of Rapicorn (and Beast) with Ubuntu distributions, intermediate summary:
>> * Recent Rapicorn and Beast build fine on Ubuntu 15.04 64bit (my development machine).
>> * On Ubuntu 14.04, Rapicorn can be built with your aida.cc fix, a bool array fix in factory.cc and simply downgrading the cython dependency from 0.20.2 to 0.20.1.
>> * For 14.04 32bit, Rapicorn is buggy, I've fixed some size_t issues locally, will push them soon.
>> * Beast does *not* build with g++-4.8 from 14.04, seems that compiler cannot handle the template stuff I needed for undo, here's a post explaining why that was quite involved: https://testbit.eu/a-day-of-templates/
>> ** I doubt this can be easily fixed, this might be the turning point where we *have* to upgrade the dependency to g++-4.9...
> I think it's acceptable to upgrade the compiler dependency to g++-4.9. This
> will save the trouble of developing a workaround for the undo usecase (a
> somewhat tricky piece of code). I tried a few easy things but failed. In any
> case I build beast now on Ubuntu-15.04 which has g++-4.9.

Ah, good you got that solved on your machine.

The compiler dependency actually gives me a bit of a headache,
I was planning/hoping to build and provide snapshot 'trusty' packages
for rapicorn and beast.
But installing and building with g++-5 from ppa:ubuntu-toolchain-r/test
also draws in new libgcc1, libstdc++, etc dependencies, so it looks like
that's simply not doable. ;-(

> Also if you think of Ubuntu LTS versions, the next one is Ubuntu-16.04 LTS.
> This is not too far in the future (half a year), so users which only use LTS
> Ubuntu will not have to wait too long until their compiler is good enough
> (again) to build beast.

Yes. Except that, in 6 months we'll badly need *some* other new compiler
feature (probably from C++14) or bugfix and the problem starts all over.

Just the way it always goes ;-)