On 2/8/2017 7:13 AM, [email protected] wrote: > > If you won't upgrade to Jessie for some reason, your code will > continue as now, but you just won't get any package updates. > > Unfortunately support has to end somewhere and Wheezy has been a > problem for some while to keep going. > Debian only make security updates to Wheezy now and next year support > will end completely.
I have been looking at the build issue with Wheezy and I hope to have it fixed soon. Currently the latest machinekit/master (with all the new multicore code) builds fine on Wheezy if you use the native gcc-4.7 compiler available in wheezy-backports (this compiler has been a requirement for a while). The problem is specific to our Docker mk-build images that do the package building. These machines have to use a cross-compiler for speed (or the builds don't complete in the allotted time for free Travis-CI) but due to assorted bad luck: http://stackoverflow.com/a/27944574 ...we don't have a proper gcc-4.7 cross tool chain and are using gcc-4.9. The build issue is a bit of missing c++ abi that got added and 4.9 is expecting to use but the 4.7 libraries we have to link with don't have the new function (__cxa_throw_bad_array_new_length). I hope to have this sorted and all package builds back to normal soon. ...but you should still consider upgrading to Jessie. ;-) -- Charles Steinkuehler [email protected] -- website: http://www.machinekit.io blog: http://blog.machinekit.io github: https://github.com/machinekit --- You received this message because you are subscribed to the Google Groups "Machinekit" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/machinekit. For more options, visit https://groups.google.com/d/optout.
