On Sat, 2012-06-16 at 19:22 -0400, lloyd wilson wrote: > Thanks for the quick reply; all files are in the same directory, which > I've tried placing in linuxcnc root and in the src directory; no change. > The find* scripts exist & are executable; find-modinc is the script that > goes thud, even if run from the command line. Since this is a C program, > not a comp, is that step needed in the make process? > > -ldw
>From this link: http://git.mah.priv.at/gitweb/vfs11-vfd.git/blob/master:/find-modinc it looks like it uses "which" to try to find "comp". if successful, it sets the "bindir" shell variable, with other variables dependent on "bindir". "which comp" at the command line should be equivalent, or "whereis comp", or just "comp" to see if comp is found. I noticed here: http://www.linuxcnc.org/index.php/english/component/kunena/?func=view&catid=10&id=18963 that LinuxCNC 2.5 now has comp in the linuxcnc-dev package rather than the older emc2-dev. http://www.linuxcnc.org/docview/html/hal/comp.html It looks like you will need to get comp running first, so find-modinc can find it. -- Kirk Wallace http://www.wallacecompany.com/machine_shop/ http://www.wallacecompany.com/E45/index.html California, USA ------------------------------------------------------------------------------ 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-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-users
