I've lost on where this is at now. I'd like to load up 12.04 LTS 32 bit and try this out.. should I wait?
Is there any good reason to use the 64 bit version? 64 bits seems to cause more problems than benefits. I'm just going to run it on a Intel D525MW board. Thanks, Dave On 9/6/2012 2:34 AM, Michael Haberler wrote: > Am 06.09.2012 um 07:26 schrieb Anders Wallin: > > >> Hi all, >> The recent redis addition has broken the build for me on 64-bit >> 12.04LTS. However Michael reported he could not reproduce on a fresh >> 12.04.(1?) install.. >> > I'll give it another stab > > what I did after importing the snapshots of the redis server and redis-py was: > > I reused the existing Makefiles of these projects untouched and 'do the right > thing' by calling them with command line options compatible with the LinuxCNC > directory structure from src/redis/Submakefile; so likely > src/redis/Submakefile is the culprit. It should be possible to reproduce the > error you see by manually calling the src/redis/redis Makfile with the proper > command line options. > > >> See below for the error. Is anyone else seeing this? >> I tried looking at the (sub)makefiles but they are not exactly >> reader-friendly. Fwiw for linuxcnc3 something better than raw >> makefiles should be used, e.g. cmake or similar. >> > I agree very much - I routinely spend a disproportionate amount of time > getting Submakefiles to work relative to actual code (like for instance, > right now :-/) That made me refrain from writing Submakefiles for > redis-server and redis-py. > > LinuxCNC isnt the only project in this situation; some are developing cmake > build instructions in parallel while leaving the existing autoconf stuff in > place until the new way stabilizes. > > Actually this project faces several major version transitions down the road > (e.g. Python3K, Gtk3, pygtk replaced by pygobject), and I dont see any work > being done on these transitions in the current source tree; it would a bit > moot anyway given package availability on current build platforms > > I think LinuxCNC3 cut is the place to start with a fresher platform where all > these packages are available from the package stream, and see how an upgraded > RTAI kernel can be slid underneath eventually - with a bit of luck and > Paolo's health and time it might happen this year. Even if that takes a while > I would go ahead with a stock rt-preempt based kernel, a recent Ubuntu > release, and not block the work on the RTAI kernel being available on day > one. Work dependent on RTAI can be done in an LinuxCNC2 branch and brought > forward once the RTAI kernel appears in a shape compatible with the newer > platform. > > That would mean that all non-LinuxCNC specific code under src/redis can go > away in LinuxCNC3 > > - Michael > > >> Anders >> >> (cd redis/redis; \ >> cd deps/linenoise; \ >> make ; \ >> cd ../.. ; \ >> make all ;\ >> cd src; \ >> make INSTALL_BIN=../../../../bin dep install) >> make[1]: Entering directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/deps/linenoise' >> make[1]: `linenoise.o' is up to date. >> make[1]: Leaving directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/deps/linenoise' >> make[1]: Entering directory `/home/anders/Desktop/emc2-dev/src/redis/redis' >> cd src&& make all >> make[2]: Entering directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/src' >> LINK redis-server >> cc: error: ../deps/jemalloc/lib/libjemalloc.a: No such file or directory >> make[2]: *** [redis-server] Error 1 >> make[2]: Leaving directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/src' >> make[1]: *** [all] Error 2 >> make[1]: Leaving directory `/home/anders/Desktop/emc2-dev/src/redis/redis' >> make[1]: Entering directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/src' >> CC dep >> LINK redis-server >> cc: error: ../deps/jemalloc/lib/libjemalloc.a: No such file or directory >> make[1]: *** [redis-server] Error 1 >> make[1]: Leaving directory >> `/home/anders/Desktop/emc2-dev/src/redis/redis/src' >> make: *** [../bin/redis-server] Error 2 >> make: Leaving directory `/home/anders/Desktop/emc2-dev/src' >> >> ------------------------------------------------------------------------------ >> Live Security Virtual Conference >> Exclusive live event will cover all the ways today's security and >> threat landscape has changed and how IT managers can respond. Discussions >> will include endpoint security, mobile security and the latest in malware >> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ >> _______________________________________________ >> Emc-developers mailing list >> Emc-developers@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-developers >> > > ------------------------------------------------------------------------------ > Live Security Virtual Conference > Exclusive live event will cover all the ways today's security and > threat landscape has changed and how IT managers can respond. Discussions > will include endpoint security, mobile security and the latest in malware > threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > > ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
