Question regarding compiling EMC BDI-4.38
I hope that you can help me with my problem regarding compiling EMC on BDI-4.38. When I use ./configure I get output: Can not compile realtime code for 2.6 series kernels. I use 2.6.12.6-rtai kernel. All configuration is originally from BDI-4.38 iso CDROM. What is to do to compile the complete package? Regards Simon Mali
Hi Sion Mali Simon ITPSD2 wrote:
I hope that you can help me with my problem regarding compiling EMC on BDI-4.38. When I use ./configure I get output:
Can not compile realtime code for 2.6 series kernels.
I use 2.6.12.6-rtai kernel. All configuration is originally from BDI-4.38 iso CDROM. What is to do to compile the complete package?
Sounds like you are trying to configure RCSLib & EMC from Sourceforge - All you can hope to successfully compile and run are the user space applications and simulation EMC. Doing "make PLAT=linux" in both rcslib/src & emc/src will build these user space components. The existing build system for EMC does not lend it's self to compiling the kernel modules (or realtime components) with any ease. This was realised very early on with the emc2 tree and it was in the bdi4 branch where 2.6 kernel support was instigated. I fyou want to compile from source, you currently have the following options: * Modify RCSLib/EMC and rewrite the make files to support 2.6 kernels. * Use the bdi4 branch of emc2 at Sourceforge. * Use the current emc-1.0-39 sources. Option 1 is probably more effort than it is worth and you don't get any of the more recent bug fixes. Option 2 is reportedly broken and last I heard, it is not recommended to do an install from the head of the emc2 tree. For option 3, add the following line to /etc/apt/sources.list deb-src http://bdi4emc.ourproject.org/debian sarge extras Run "sudo apt-get update" and then you can download the current emc-1.0 sources with "apt-get source emc" - This gets you a reworked code base using the emc2 directory layout, libnml, a subset of the original EMC sources, and a make system designed to work with 2.6 kernels. As an added bonus, you also get a number of bug fixes not found in the original EMC tree. Regards, Paul.
On Thu, Mar 02, 2006 at 04:24:47PM +0000, Paul wrote:
Option 2 is reportedly broken and last I heard, it is not recommended to do an install from the head of the emc2 tree.
That's right. For BDI systems, I think the best way to try emc2 is to use "run in place". This won't write any files outside of the emc2 directory, so you won't "overwrite" anything. After checking out the HEAD or TESTING version of emc2, and installing the additional development packages needed, you configure and build it like this: cd emc2/src ./configure --enable-run-in-place make && sudo make install Then, in the emc2 directory you run scripts/emc2 and can choose a configuration file from the menu. One of the two machines I use to develop AXIS is BDI4. I test AXIS against emc2, as well as Paul's version of emc. If you run into problems building or using emc2 on a bdi4 system, the developers of emc2 would like to know about it. Jeff
I made a mistake in the instructions for installing emc2 on a bdi system. Use "sudo make setuid", not "sudo make install".
After checking out the HEAD or TESTING version of emc2, and installing the additional development packages needed, you configure and build it like this: cd emc2/src ./configure --enable-run-in-place make && sudo make setuid # ^^^^^^ Then, in the emc2 directory you run scripts/emc2 and can choose a configuration file from the menu.
participants (3)
-
jepler＠unpythonic.net -
Mali Simon ITPSD2 -
Paul