Re: [Emc-users] [emc-users] Building from source
On Wed, May 10, 2017 at 10:07 AM, Sebastian Kuzminskywrote: > On 05/09/2017 10:15 PM, Evan Foss wrote: >> On Wed, May 10, 2017 at 3:13 AM, Evan Foss wrote: >>> On Sun, May 7, 2017 at 1:09 PM, suavesteve wrote: I've come across this earlier and had created a local patch, >>> >>> Would you please dig that patch out and share it? >>> Tested with both v3.0.6 and v3.1.4 (Latest Stable release) >>> >>> Thanks! >> >> Your patch for libmodplug works so linuxcnc-2.7.8 now fails at install >> instead of build (just like the git head). I am going to call that a >> win. > > Beware there's a bug in that patch: it builds, but it makes the timeout > wrong. I've asked suavesteve to update it. I appreciate the warning but if you are talking about a communications timeout I don't care since people are only going to use it for simulation and for the gerber processing library. I will warn people that if they intend on using it to run a real machine they need to use the OS image linuxcnc provides. >> this is what the make install produces >> >> Makefile:536: warning: undefined variable 'DESTDIR' > > We recommend against running "make install", unless you're building > binary packages for distribution. The reason for that recommendation is > that "make install" copies the linuxcnc build products into your system > without any kind of tracking, so you can't easily uninstall them later, > and if a future version of linuxcnc *stops* installing a file, the old > one will be left behind when you upgrade. > > We recommend instead building managed binary packages (like our .debs) > or using the "run-in-place" feature of our build system, and running > linuxcnc out of the build directory, without installing. Ok I will look at that again tonight. > If you still want to make install, set the DESTDIR environment variable > to the directory you want to install into. Something like > "DESTDIR=/home/user1/programs/linuxcnc make install". > > Depending on where the DESTDIR path is, you may need root permissions to > write there. I tried that and it still was determined to shove stuff into /. The directory i was using is in my home and I have the permissions set correctly. > > -- > Sebastian Kuzminsky > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -END PGP PUBLIC KEY BLOCK- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On 05/09/2017 10:15 PM, Evan Foss wrote: > On Wed, May 10, 2017 at 3:13 AM, Evan Fosswrote: >> On Sun, May 7, 2017 at 1:09 PM, suavesteve wrote: >>> I've come across this earlier and had created a local patch, >> >> Would you please dig that patch out and share it? >> >>> Tested with both v3.0.6 and v3.1.4 (Latest Stable release) >>> >> >> Thanks! > > Your patch for libmodplug works so linuxcnc-2.7.8 now fails at install > instead of build (just like the git head). I am going to call that a > win. Beware there's a bug in that patch: it builds, but it makes the timeout wrong. I've asked suavesteve to update it. > this is what the make install produces > > Makefile:536: warning: undefined variable 'DESTDIR' We recommend against running "make install", unless you're building binary packages for distribution. The reason for that recommendation is that "make install" copies the linuxcnc build products into your system without any kind of tracking, so you can't easily uninstall them later, and if a future version of linuxcnc *stops* installing a file, the old one will be left behind when you upgrade. We recommend instead building managed binary packages (like our .debs) or using the "run-in-place" feature of our build system, and running linuxcnc out of the build directory, without installing. If you still want to make install, set the DESTDIR environment variable to the directory you want to install into. Something like "DESTDIR=/home/user1/programs/linuxcnc make install". Depending on where the DESTDIR path is, you may need root permissions to write there. -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Wed, May 10, 2017 at 5:29 AM, andy pughwrote: > On 10 May 2017 at 05:15, Evan Foss wrote: >> Your patch for libmodplug works so linuxcnc-2.7.8 now fails at install >> instead of build (just like the git head). I am going to call that a >> win. > > --prefix _might_ help with that. I am using that.. as i already said this is the line i am using to configure linuxcnc ./configure --enable-simulator --with-python=/usr/bin/python2.7 --with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc > -- > atp > "A motorcycle is a bicycle with a pandemonium attachment and is > designed for the especial use of mechanical geniuses, daredevils and > lunatics." > — George Fitch, Atlanta Constitution Newspaper, 1916 > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -END PGP PUBLIC KEY BLOCK- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On 10 May 2017 at 05:15, Evan Fosswrote: > Your patch for libmodplug works so linuxcnc-2.7.8 now fails at install > instead of build (just like the git head). I am going to call that a > win. --prefix _might_ help with that. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Wed, May 10, 2017 at 3:13 AM, Evan Fosswrote: > On Sun, May 7, 2017 at 1:09 PM, suavesteve wrote: >> I've come across this earlier and had created a local patch, > > Would you please dig that patch out and share it? > >> Tested with both v3.0.6 and v3.1.4 (Latest Stable release) >> > > Thanks! Your patch for libmodplug works so linuxcnc-2.7.8 now fails at install instead of build (just like the git head). I am going to call that a win. this is what the make install produces Makefile:536: warning: undefined variable 'DESTDIR' Makefile:536: warning: undefined variable 'DESTDIR' Makefile:536: warning: undefined variable 'DESTDIR' Makefile:688: warning: undefined variable 'DESTDIR' Makefile:688: warning: undefined variable 'DESTDIR' Makefile:688: warning: undefined variable 'DESTDIR' Makefile:689: warning: undefined variable 'DESTDIR' Makefile:690: warning: undefined variable 'DESTDIR' Makefile:691: warning: undefined variable 'DESTDIR' install -d -m 0755 -o root /home/user1/programs/linuxcnc/lib/linuxcnc/modules/linuxcnc \ /home/user1/programs/linuxcnc/bin \ /home/user1/programs/linuxcnc/etc/linuxcnc install: cannot change owner and permissions of ‘/home/user1/programs/linuxcnc/lib/linuxcnc/modules/linuxcnc’: Operation not permitted install: cannot change owner and permissions of ‘/home/user1/programs/linuxcnc/bin’: Operation not permitted install: cannot change owner and permissions of ‘/home/user1/programs/linuxcnc/etc/linuxcnc’: Operation not permitted make: *** [Makefile:688: install-kernel-dep] Error 1 >> >> Philip >> >> Evan Foss writes: >> >>> Is anyone looking into this? >>> >>> On Thu, Apr 27, 2017 at 3:49 AM, Evan Foss wrote: On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminsky wrote: > 2.7 should build anywhere the master branch (2.8-prerelease) builds, what > build error do you get? Attached are the configure and build runs. I tried playing with the --enable-non-distributable=yes option but it still lands on the same error. This is just the error extracted from the build. Compiling hal/user_comps/mb2hal/mb2hal.c hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of ‘modbus_set_response_timeout’ makes integer from pointer without a cast [enabled by default] In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but argument is of type ‘struct timeval *’ hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to function ‘modbus_set_response_timeout’ In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:188:16: note: declared here hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of ‘modbus_set_byte_timeout’ makes integer from pointer without a cast [enabled by default] In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but argument is of type ‘struct timeval *’ hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to function ‘modbus_set_byte_timeout’ In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:191:16: note: declared here make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] Error 1 > And how does matter fail to run? 2.8-prerelease has some quirks you should know. (or perhaps i am miss using it) 1. It doesn't understand --prefix= as other packages seem too in my experience. When I went to do make install it complained about not having a DESTDIR so I added DESTDIR := / to the Makefile. 2. It doesn't understand that when --prefix= points to say /home/username/programs/whatever/ that it has to use the installers permission level. (it kept bugging me for root) I added the following to my .bashrc because it is not installed in / export PATH=/home/user1/programs/linuxcnc/bin:${PATH} export LD_LIBRARY_PATH=/home/user1/programs/linuxcnc/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=/home/user1/programs/linuxcnc/lib/pkgconfig:$PKG_CONFIG_PATH When I run this is what happens in the console. In the gui The LinuxCNC Configuration Selector CURRENT: axis.ini. I leave it on axis.ini and click Next. When it crashes. ~ $ linuxcnc LINUXCNC - 2.8.0~pre1 Machine configuration directory is
Re: [Emc-users] [emc-users] Building from source
On Sun, May 7, 2017 at 1:09 PM, suavestevewrote: > I've come across this earlier and had created a local patch, Would you please dig that patch out and share it? > Tested with both v3.0.6 and v3.1.4 (Latest Stable release) > Thanks! > > Philip > > Evan Foss writes: > >> Is anyone looking into this? >> >> On Thu, Apr 27, 2017 at 3:49 AM, Evan Foss wrote: >>> On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminsky >>> wrote: 2.7 should build anywhere the master branch (2.8-prerelease) builds, what build error do you get? >>> >>> Attached are the configure and build runs. I tried playing with the >>> --enable-non-distributable=yes option but it still lands on the same >>> error. >>> This is just the error extracted from the build. >>> >>> Compiling hal/user_comps/mb2hal/mb2hal.c >>> hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: >>> hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of >>> ‘modbus_set_response_timeout’ makes integer from pointer without a >>> cast [enabled by default] >>> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >>> from hal/user_comps/mb2hal/mb2hal.c:27: >>> /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but >>> argument is of type ‘struct timeval *’ >>> hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to >>> function ‘modbus_set_response_timeout’ >>> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >>> from hal/user_comps/mb2hal/mb2hal.c:27: >>> /usr/include/modbus/modbus.h:188:16: note: declared here >>> hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of >>> ‘modbus_set_byte_timeout’ makes integer from pointer without a cast >>> [enabled by default] >>> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >>> from hal/user_comps/mb2hal/mb2hal.c:27: >>> /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but >>> argument is of type ‘struct timeval *’ >>> hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to >>> function ‘modbus_set_byte_timeout’ >>> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >>> from hal/user_comps/mb2hal/mb2hal.c:27: >>> /usr/include/modbus/modbus.h:191:16: note: declared here >>> make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] Error 1 >>> >>> And how does matter fail to run? >>> >>> 2.8-prerelease has some quirks you should know. (or perhaps i am miss using >>> it) >>> 1. It doesn't understand --prefix= as other packages seem too in my >>> experience. When I went to do make install it complained about not >>> having a DESTDIR so I added DESTDIR := / to the Makefile. >>> 2. It doesn't understand that when --prefix= points to say >>> /home/username/programs/whatever/ that it has to use the installers >>> permission level. (it kept bugging me for root) >>> >>> I added the following to my .bashrc because it is not installed in / >>> export PATH=/home/user1/programs/linuxcnc/bin:${PATH} >>> export LD_LIBRARY_PATH=/home/user1/programs/linuxcnc/lib:$LD_LIBRARY_PATH >>> export >>> PKG_CONFIG_PATH=/home/user1/programs/linuxcnc/lib/pkgconfig:$PKG_CONFIG_PATH >>> >>> When I run this is what happens in the console. In the gui The >>> LinuxCNC Configuration Selector CURRENT: axis.ini. >>> I leave it on axis.ini and click Next. When it crashes. >>> >>> ~ $ linuxcnc >>> LINUXCNC - 2.8.0~pre1 >>> Machine configuration directory is >>> '/home/user1/programs/linuxcnc/share/doc/linuxcnc/examples/sample-configs/sim/axis' >>> Machine configuration file is 'axis.ini' >>> can't find package Linuxcnc >>> while executing >>> "package require Linuxcnc " >>> (file >>> "/home/user1/programs/linuxcnc/share/linuxcnc/hallib/check_config.tcl" >>> line 83) >>> check_config validation failed >>> LinuxCNC terminated with an error. You can find more information in the >>> log: >>> /home/user1/linuxcnc_debug.txt >>> and >>> /home/user1/linuxcnc_print.txt >>> as well as in the output of the shell command 'dmesg' and in the terminal >>> >>> I attached linuxcnc_print.txt but linuxcnc_debug.txt is empty (0 bytes). >>> >>> Thanks for the continued effort, >>> Evan (and the rest of the pcb-rnd team) >>> On April 25, 2017 7:01:29 PM MDT, Evan Foss wrote: > > On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminsky > wrote: >> >> On 04/23/2017 09:25 PM, Evan Foss wrote: >>> >>> Ok so I tried >>> LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus >>> --with-realtime=uspace --with-python=/usr/bin/python2.7 >>> --with-boost-python=py27 >>> (all one line) and it still lands in the same failure. I attached the >>> logfile >> >> >> Chris Radek pointed out to me on IRC that i'd given you the wrong >> boost-python library name. That command line
Re: [Emc-users] [emc-users] Building from source
On 05/07/2017 07:09 AM, suavesteve wrote: > I've come across this earlier and had created a local patch, > > Tested with both v3.0.6 and v3.1.4 (Latest Stable release) Thanks Philip/suavesteve for posting that! It's strange to me that the libmodbus folks went from using a struct timeval for their timeout to passing the fields individually, but sure enough they did. According to http://libmodbus.org, 3.0 is stable and 3.1 is still listed as unstable, even though it's been around for years and has had several stable-looking "releases". Some feedback on your patch: You pass timeout.tv_sec for both the seconds and the microseconds, I think you meant to pass timeout.tv_usec for the third argument. Details on that here: http://libmodbus.org/docs/v3.1.4/modbus_set_response_timeout.html Instead of taking the pointer of timeout and dereferencing it ("(uint32_t) ()->tv_sec"), it's simpler and clearer to just use the field directly ("(uint32_t)timeout.tv_sec"). There's a bug in the #if you use for version detection, think about (for example) a hypothetical future version 4.0. Use LIBMODBUS_VERSION_HEX instead of LIBMODBUS_VERSION_MAJOR and LIBMODBUS_VERSION_MINOR. Instead of this: +#if LIBMODBUS_VERSION_MAJOR >= 3 && LIBMODBUS_VERSION_MINOR >= 1 Use this (untested): +#if LIBMODBUS_VERSION_HEX >= 0x0301 If you make those changes, and sign off on your commit (see http://linuxcnc.org/docs/devel/html/code/contributing-to-linuxcnc.html#_signed_off_by_policy), then I'll gladly apply your patch in LinuxCNC 2.7. -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
I've come across this earlier and had created a local patch, Tested with both v3.0.6 and v3.1.4 (Latest Stable release) >From 0b557f7116cd52a2b69e84872588e22577c1b459 Mon Sep 17 00:00:00 2001 From: Philip MullenDate: Sun, 7 May 2017 13:52:53 +0100 Subject: [PATCH] Add support for libmodbus >= v3.1 Added support for the new form of modbus_set_response_timeout and modbus_set_byte_timeout in versions >= 3.1 --- src/hal/user_comps/mb2hal/mb2hal.c | 18 ++ 1 file changed, 14 insertions(+), 4 deletions(-) diff --git a/src/hal/user_comps/mb2hal/mb2hal.c b/src/hal/user_comps/mb2hal/mb2hal.c index 1ba9a87..1ca067e 100644 --- a/src/hal/user_comps/mb2hal/mb2hal.c +++ b/src/hal/user_comps/mb2hal/mb2hal.c @@ -355,18 +355,28 @@ retCode get_tx_connection(const int this_mb_tx_num, int *ret_connected) //set the low level mb_link debug according to each mb_tx modbus_set_debug(this_mb_link->modbus, this_mb_tx->protocol_debug); - -//set response and byte timeout according to each mb_tx timeout.tv_sec = this_mb_tx->mb_response_timeout_ms / 1000; timeout.tv_usec = (this_mb_tx->mb_response_timeout_ms % 1000) * 1000; -modbus_set_response_timeout(this_mb_link->modbus, ); +//set response and byte timeout according to each mb_tx +#if LIBMODBUS_VERSION_MAJOR >= 3 && LIBMODBUS_VERSION_MINOR >= 1 +modbus_set_response_timeout(this_mb_link->modbus, (uint32_t) ()->tv_sec, (uint32_t) ()->tv_sec); +#else +modbus_set_response_timeout(this_mb_link->modbus, ); +#endif // LIBMODBUS_VERSION + //DBG(this_mb_tx->cfg_debug, "mb_tx_num[%d] mb_links[%d] response timeout [%d] ([%d] [%d])", //this_mb_tx_num, this_mb_tx->mb_link_num, this_mb_tx->mb_response_timeout_ms, //(int) timeout.tv_sec, (int) timeout.tv_usec); timeout.tv_sec = this_mb_tx->mb_byte_timeout_ms / 1000; timeout.tv_usec = (this_mb_tx->mb_byte_timeout_ms % 1000) * 1000; -modbus_set_byte_timeout(this_mb_link->modbus, ); + +#if LIBMODBUS_VERSION_MAJOR >= 3 && LIBMODBUS_VERSION_MINOR >= 1 +modbus_set_byte_timeout(this_mb_link->modbus, (uint32_t) ()->tv_sec, (uint32_t) ()->tv_sec); +#else +modbus_set_byte_timeout(this_mb_link->modbus, ); +#endif // LIBMODBUS_VERSION + //DBG(this_mb_tx->cfg_debug, "mb_tx_num[%d] mb_links[%d] byte timeout [%d] ([%d] [%d])", //this_mb_tx_num, this_mb_tx->mb_link_num, this_mb_tx->mb_byte_timeout_ms, //(int) timeout.tv_sec, (int) timeout.tv_usec); -- 2.9.3 Philip Evan Foss writes: > Is anyone looking into this? > > On Thu, Apr 27, 2017 at 3:49 AM, Evan Foss wrote: >> On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminsky >> wrote: >>> 2.7 should build anywhere the master branch (2.8-prerelease) builds, what >>> build error do you get? >> >> Attached are the configure and build runs. I tried playing with the >> --enable-non-distributable=yes option but it still lands on the same >> error. >> This is just the error extracted from the build. >> >> Compiling hal/user_comps/mb2hal/mb2hal.c >> hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: >> hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of >> ‘modbus_set_response_timeout’ makes integer from pointer without a >> cast [enabled by default] >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but >> argument is of type ‘struct timeval *’ >> hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to >> function ‘modbus_set_response_timeout’ >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:188:16: note: declared here >> hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of >> ‘modbus_set_byte_timeout’ makes integer from pointer without a cast >> [enabled by default] >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but >> argument is of type ‘struct timeval *’ >> hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to >> function ‘modbus_set_byte_timeout’ >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:191:16: note: declared here >> make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] Error 1 >> >> >>> And how does matter fail to run? >> >> 2.8-prerelease has some quirks you should know. (or perhaps i am miss using >> it) >> 1. It doesn't understand --prefix= as other packages seem too in my >> experience. When I went to do make install it complained about not >> having a DESTDIR so I added DESTDIR := /
Re: [Emc-users] [emc-users] Building from source
You're the only one I know of who's looking into this. I see that you're using libmodbus 3.1.2, all we build and test on is various 3.0 versions. It looks like an API function changed between 3.0 and 3.1, so you have the options: 1. Build without modbus support. 2. Figure out how to use the new libmodbus interface. 3. Downgrade your build system to libmodbus 3.0. If you decide to add support for libmodbus 3.1, please send a PR against the master branch. On May 6, 2017 4:07:06 PM MDT, Evan Fosswrote: >Is anyone looking into this? > >On Thu, Apr 27, 2017 at 3:49 AM, Evan Foss wrote: >> On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminsky > wrote: >>> 2.7 should build anywhere the master branch (2.8-prerelease) builds, >what >>> build error do you get? >> >> Attached are the configure and build runs. I tried playing with the >> --enable-non-distributable=yes option but it still lands on the same >> error. >> This is just the error extracted from the build. >> >> Compiling hal/user_comps/mb2hal/mb2hal.c >> hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: >> hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of >> ‘modbus_set_response_timeout’ makes integer from pointer without a >> cast [enabled by default] >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but >> argument is of type ‘struct timeval *’ >> hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to >> function ‘modbus_set_response_timeout’ >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:188:16: note: declared here >> hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of >> ‘modbus_set_byte_timeout’ makes integer from pointer without a cast >> [enabled by default] >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but >> argument is of type ‘struct timeval *’ >> hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to >> function ‘modbus_set_byte_timeout’ >> In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, >> from hal/user_comps/mb2hal/mb2hal.c:27: >> /usr/include/modbus/modbus.h:191:16: note: declared here >> make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] >Error 1 >> >> >>> And how does matter fail to run? >> >> 2.8-prerelease has some quirks you should know. (or perhaps i am miss >using it) >> 1. It doesn't understand --prefix= as other packages seem too in my >> experience. When I went to do make install it complained about not >> having a DESTDIR so I added DESTDIR := / to the Makefile. >> 2. It doesn't understand that when --prefix= points to say >> /home/username/programs/whatever/ that it has to use the installers >> permission level. (it kept bugging me for root) >> >> I added the following to my .bashrc because it is not installed in / >> export PATH=/home/user1/programs/linuxcnc/bin:${PATH} >> export >LD_LIBRARY_PATH=/home/user1/programs/linuxcnc/lib:$LD_LIBRARY_PATH >> export >PKG_CONFIG_PATH=/home/user1/programs/linuxcnc/lib/pkgconfig:$PKG_CONFIG_PATH >> >> When I run this is what happens in the console. In the gui The >> LinuxCNC Configuration Selector CURRENT: axis.ini. >> I leave it on axis.ini and click Next. When it crashes. >> >> ~ $ linuxcnc >> LINUXCNC - 2.8.0~pre1 >> Machine configuration directory is >> >'/home/user1/programs/linuxcnc/share/doc/linuxcnc/examples/sample-configs/sim/axis' >> Machine configuration file is 'axis.ini' >> can't find package Linuxcnc >> while executing >> "package require Linuxcnc " >> (file >"/home/user1/programs/linuxcnc/share/linuxcnc/hallib/check_config.tcl" >> line 83) >> check_config validation failed >> LinuxCNC terminated with an error. You can find more information in >the log: >> /home/user1/linuxcnc_debug.txt >> and >> /home/user1/linuxcnc_print.txt >> as well as in the output of the shell command 'dmesg' and in the >terminal >> >> I attached linuxcnc_print.txt but linuxcnc_debug.txt is empty (0 >bytes). >> >> Thanks for the continued effort, >> Evan (and the rest of the pcb-rnd team) >> >>> >>> On April 25, 2017 7:01:29 PM MDT, Evan Foss >wrote: On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminsky > wrote: > > On 04/23/2017 09:25 PM, Evan Foss wrote: >> >> Ok so I tried >> LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus >> --with-realtime=uspace --with-python=/usr/bin/python2.7 >> --with-boost-python=py27 >> (all one line) and it still lands in the same failure. I >attached the >> logfile > > > Chris Radek
Re: [Emc-users] [emc-users] Building from source
Is anyone looking into this? On Thu, Apr 27, 2017 at 3:49 AM, Evan Fosswrote: > On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminsky wrote: >> 2.7 should build anywhere the master branch (2.8-prerelease) builds, what >> build error do you get? > > Attached are the configure and build runs. I tried playing with the > --enable-non-distributable=yes option but it still lands on the same > error. > This is just the error extracted from the build. > > Compiling hal/user_comps/mb2hal/mb2hal.c > hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: > hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of > ‘modbus_set_response_timeout’ makes integer from pointer without a > cast [enabled by default] > In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, > from hal/user_comps/mb2hal/mb2hal.c:27: > /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but > argument is of type ‘struct timeval *’ > hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to > function ‘modbus_set_response_timeout’ > In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, > from hal/user_comps/mb2hal/mb2hal.c:27: > /usr/include/modbus/modbus.h:188:16: note: declared here > hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of > ‘modbus_set_byte_timeout’ makes integer from pointer without a cast > [enabled by default] > In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, > from hal/user_comps/mb2hal/mb2hal.c:27: > /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but > argument is of type ‘struct timeval *’ > hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to > function ‘modbus_set_byte_timeout’ > In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, > from hal/user_comps/mb2hal/mb2hal.c:27: > /usr/include/modbus/modbus.h:191:16: note: declared here > make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] Error 1 > > >> And how does matter fail to run? > > 2.8-prerelease has some quirks you should know. (or perhaps i am miss using > it) > 1. It doesn't understand --prefix= as other packages seem too in my > experience. When I went to do make install it complained about not > having a DESTDIR so I added DESTDIR := / to the Makefile. > 2. It doesn't understand that when --prefix= points to say > /home/username/programs/whatever/ that it has to use the installers > permission level. (it kept bugging me for root) > > I added the following to my .bashrc because it is not installed in / > export PATH=/home/user1/programs/linuxcnc/bin:${PATH} > export LD_LIBRARY_PATH=/home/user1/programs/linuxcnc/lib:$LD_LIBRARY_PATH > export > PKG_CONFIG_PATH=/home/user1/programs/linuxcnc/lib/pkgconfig:$PKG_CONFIG_PATH > > When I run this is what happens in the console. In the gui The > LinuxCNC Configuration Selector CURRENT: axis.ini. > I leave it on axis.ini and click Next. When it crashes. > > ~ $ linuxcnc > LINUXCNC - 2.8.0~pre1 > Machine configuration directory is > '/home/user1/programs/linuxcnc/share/doc/linuxcnc/examples/sample-configs/sim/axis' > Machine configuration file is 'axis.ini' > can't find package Linuxcnc > while executing > "package require Linuxcnc " > (file > "/home/user1/programs/linuxcnc/share/linuxcnc/hallib/check_config.tcl" > line 83) > check_config validation failed > LinuxCNC terminated with an error. You can find more information in the log: > /home/user1/linuxcnc_debug.txt > and > /home/user1/linuxcnc_print.txt > as well as in the output of the shell command 'dmesg' and in the terminal > > I attached linuxcnc_print.txt but linuxcnc_debug.txt is empty (0 bytes). > > Thanks for the continued effort, > Evan (and the rest of the pcb-rnd team) > >> >> On April 25, 2017 7:01:29 PM MDT, Evan Foss wrote: >>> >>> On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminsky >>> wrote: On 04/23/2017 09:25 PM, Evan Foss wrote: > > Ok so I tried > LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus > --with-realtime=uspace --with-python=/usr/bin/python2.7 > --with-boost-python=py27 > (all one line) and it still lands in the same failure. I attached the > logfile Chris Radek pointed out to me on IRC that i'd given you the wrong boost-python library name. That command line is right except it should be --with-boost-python=2.7, *not* =py2.7. >>> >>> >>> You and Chris Radek ROCK! This worked past the configure stage but now >>> i have a different problem... >>> ./configure --enable-simulator --with-python=/usr/bin/python2.7 >>> --with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc >>> >>> Using release 2.7.8 the build fails. Using the current git head it >>> builds but fails run. Which should I focus on? >>> -- Sebastian Kuzminsky
Re: [Emc-users] [emc-users] Building from source
On Wed, Apr 26, 2017 at 1:30 PM, Sebastian Kuzminskywrote: > 2.7 should build anywhere the master branch (2.8-prerelease) builds, what > build error do you get? Attached are the configure and build runs. I tried playing with the --enable-non-distributable=yes option but it still lands on the same error. This is just the error extracted from the build. Compiling hal/user_comps/mb2hal/mb2hal.c hal/user_comps/mb2hal/mb2hal.c: In function ‘get_tx_connection’: hal/user_comps/mb2hal/mb2hal.c:362:5: warning: passing argument 2 of ‘modbus_set_response_timeout’ makes integer from pointer without a cast [enabled by default] In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:188:16: note: expected ‘uint32_t’ but argument is of type ‘struct timeval *’ hal/user_comps/mb2hal/mb2hal.c:362:5: error: too few arguments to function ‘modbus_set_response_timeout’ In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:188:16: note: declared here hal/user_comps/mb2hal/mb2hal.c:369:5: warning: passing argument 2 of ‘modbus_set_byte_timeout’ makes integer from pointer without a cast [enabled by default] In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:191:16: note: expected ‘uint32_t’ but argument is of type ‘struct timeval *’ hal/user_comps/mb2hal/mb2hal.c:369:5: error: too few arguments to function ‘modbus_set_byte_timeout’ In file included from hal/user_comps/mb2hal/mb2hal.h:18:0, from hal/user_comps/mb2hal/mb2hal.c:27: /usr/include/modbus/modbus.h:191:16: note: declared here make: *** [Makefile:211: objects/hal/user_comps/mb2hal/mb2hal.o] Error 1 > And how does matter fail to run? 2.8-prerelease has some quirks you should know. (or perhaps i am miss using it) 1. It doesn't understand --prefix= as other packages seem too in my experience. When I went to do make install it complained about not having a DESTDIR so I added DESTDIR := / to the Makefile. 2. It doesn't understand that when --prefix= points to say /home/username/programs/whatever/ that it has to use the installers permission level. (it kept bugging me for root) I added the following to my .bashrc because it is not installed in / export PATH=/home/user1/programs/linuxcnc/bin:${PATH} export LD_LIBRARY_PATH=/home/user1/programs/linuxcnc/lib:$LD_LIBRARY_PATH export PKG_CONFIG_PATH=/home/user1/programs/linuxcnc/lib/pkgconfig:$PKG_CONFIG_PATH When I run this is what happens in the console. In the gui The LinuxCNC Configuration Selector CURRENT: axis.ini. I leave it on axis.ini and click Next. When it crashes. ~ $ linuxcnc LINUXCNC - 2.8.0~pre1 Machine configuration directory is '/home/user1/programs/linuxcnc/share/doc/linuxcnc/examples/sample-configs/sim/axis' Machine configuration file is 'axis.ini' can't find package Linuxcnc while executing "package require Linuxcnc " (file "/home/user1/programs/linuxcnc/share/linuxcnc/hallib/check_config.tcl" line 83) check_config validation failed LinuxCNC terminated with an error. You can find more information in the log: /home/user1/linuxcnc_debug.txt and /home/user1/linuxcnc_print.txt as well as in the output of the shell command 'dmesg' and in the terminal I attached linuxcnc_print.txt but linuxcnc_debug.txt is empty (0 bytes). Thanks for the continued effort, Evan (and the rest of the pcb-rnd team) > > On April 25, 2017 7:01:29 PM MDT, Evan Foss wrote: >> >> On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminsky >> wrote: >>> >>> On 04/23/2017 09:25 PM, Evan Foss wrote: Ok so I tried LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus --with-realtime=uspace --with-python=/usr/bin/python2.7 --with-boost-python=py27 (all one line) and it still lands in the same failure. I attached the logfile >>> >>> >>> Chris Radek pointed out to me on IRC that i'd given you the wrong >>> boost-python library name. That command line is right except it should >>> be --with-boost-python=2.7, *not* =py2.7. >> >> >> You and Chris Radek ROCK! This worked past the configure stage but now >> i have a different problem... >> ./configure --enable-simulator --with-python=/usr/bin/python2.7 >> --with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc >> >> Using release 2.7.8 the build fails. Using the current git head it >> builds but fails run. Which should I focus on? >> >>> >>> -- >>> Sebastian Kuzminsky >>> >>> >>> >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> >>> >>> Emc-users mailing list >>> Emc-users@lists.sourceforge.net >>>
Re: [Emc-users] [emc-users] Building from source
2.7 should build anywhere the master branch (2.8-prerelease) builds, what build error do you get? And how does matter fail to run? On April 25, 2017 7:01:29 PM MDT, Evan Fosswrote: >On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminsky >wrote: >> On 04/23/2017 09:25 PM, Evan Foss wrote: >>> Ok so I tried >>> LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus >>> --with-realtime=uspace --with-python=/usr/bin/python2.7 >>> --with-boost-python=py27 >>> (all one line) and it still lands in the same failure. I attached >the logfile >> >> Chris Radek pointed out to me on IRC that i'd given you the wrong >> boost-python library name. That command line is right except it >should >> be --with-boost-python=2.7, *not* =py2.7. > >You and Chris Radek ROCK! This worked past the configure stage but now >i have a different problem... >./configure --enable-simulator --with-python=/usr/bin/python2.7 >--with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc > >Using release 2.7.8 the build fails. Using the current git head it >builds but fails run. Which should I focus on? > >> >> -- >> Sebastian Kuzminsky >> >> >-- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users > > > >-- >Home >http://evanfoss.googlepages.com/ >Work >http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ > >-BEGIN PGP PUBLIC KEY BLOCK- >Version: GnuPG v2 > >mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai >VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd >hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE >JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 >stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go >bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp >cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC >ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN >bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X >tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj >XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 >APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ >3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC >qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 >SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M >K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 >A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk >5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ >xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er >ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 >Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 >0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D >gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 >CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD >fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 >EY347EidAw== >=Ta4p >-END PGP PUBLIC KEY BLOCK- -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Mon, Apr 24, 2017 at 2:49 PM, Sebastian Kuzminskywrote: > On 04/23/2017 09:25 PM, Evan Foss wrote: >> Ok so I tried >> LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus >> --with-realtime=uspace --with-python=/usr/bin/python2.7 >> --with-boost-python=py27 >> (all one line) and it still lands in the same failure. I attached the logfile > > Chris Radek pointed out to me on IRC that i'd given you the wrong > boost-python library name. That command line is right except it should > be --with-boost-python=2.7, *not* =py2.7. You and Chris Radek ROCK! This worked past the configure stage but now i have a different problem... ./configure --enable-simulator --with-python=/usr/bin/python2.7 --with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc Using release 2.7.8 the build fails. Using the current git head it builds but fails run. Which should I focus on? > > -- > Sebastian Kuzminsky > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -END PGP PUBLIC KEY BLOCK- This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by LinuxCNC configure 2.8.0~pre1, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --enable-simulator --with-python=/usr/bin/python2.7 --with-boost-python=2.7 --prefix=/home/user1/programs/linuxcnc ## - ## ## Platform. ## ## - ## hostname = turingatlarge uname -m = x86_64 uname -r = 4.9.16-gentoo uname -s = Linux uname -v = #2 SMP Sun Apr 2 02:22:32 UTC 2017 /usr/bin/uname -p = Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine = unknown /usr/bin/oslevel = unknown /bin/universe = unknown PATH: /home/user1/programs/pcb-rnd-svn/bin PATH: /usr/local/bin PATH: /usr/bin PATH: /bin PATH: /opt/bin PATH: /usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3 PATH: /usr/lib64/opencascade-6.7.1/ros/lin/bin PATH: /usr/games/bin ## --- ## ## Core tests. ## ## --- ## configure:2623: checking for g++ configure:2639: found /usr/bin/g++ configure:2650: result: g++ configure:2677: checking for C++ compiler version configure:2686: g++ --version >&5 g++ (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) 4.7.3 Copyright (C) 2012 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. configure:2697: $? = 0 configure:2686: g++ -v >&5 Using built-in specs. COLLECT_GCC=/usr/x86_64-pc-linux-gnu/gcc-bin/4.7.3/g++ COLLECT_LTO_WRAPPER=/usr/libexec/gcc/x86_64-pc-linux-gnu/4.7.3/lto-wrapper Target: x86_64-pc-linux-gnu Configured with:
Re: [Emc-users] [emc-users] Building from source
On 04/23/2017 09:25 PM, Evan Foss wrote: > Ok so I tried > LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus > --with-realtime=uspace --with-python=/usr/bin/python2.7 > --with-boost-python=py27 > (all one line) and it still lands in the same failure. I attached the logfile Chris Radek pointed out to me on IRC that i'd given you the wrong boost-python library name. That command line is right except it should be --with-boost-python=2.7, *not* =py2.7. -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Mon, Apr 24, 2017 at 1:38 AM, Evan Fosswrote: > On Sun, Apr 23, 2017 at 5:56 PM, Sebastian Kuzminsky wrote: >> This looks closer, the relevant part from the config.log is this: >> >> configure:8072: g++ -o conftest -g -O2 -std=c++11 -I/usr/include/python2.7 >> conftest.cpp -lXinerama -lpython2.7 -lboost_python-py27 >&5 >> /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: >> cannot find -lboost_python-py27 collect2: error: ld returned 1 exit status >> >> So it's looking for the correct library name now, and you said earlier you >> have it here: >> >> /usr/lib64/libboost_python-2.7.so > > Yep that file is there. > >> So try adding LDFLAGS=-L/usr/lib64, either as an environment variable or via >> the configure flag. > > I tried this... > ./configure --without-libmodbus --with-realtime=uspace > --with-python=/usr/bin/python2.7 --with-boost-python > LDFLAGS=-L/usr/lib/64 > and later this for good measure... > export LDFLAGS=-L/usr/lib64 > > Sadly I still get this... > checking for xgettext tcl bug... xgettext version 0.19.7 OK > checking for msgfmt... /usr/bin/msgfmt > checking for --tcl support in msgfmt... yes > checking for Python support... yes > checking python version... OK > checking version of python libraries... python2.7 > checking match between tk and Tkinter versions... 8.5 > checking location of Python header files... /usr/include/python2.7 > checking for Python headers... -I/usr/include/python2.7 > checking for Python libraries... -lpthread -ldl -lutil > checking whether the Boost::Python headers are available... yes > checking for boost::python shared library... > configure: error: boost::python is required to build LinuxCNC > > attached is the config.log > based on what you said I found this > configure:8072: g++ -o conftest -g -O2 -std=c++11 > -I/usr/include/python2.7 -L/usr/lib/64 conftest.cpp -lXinerama > -lpython2.7 -lboost_python-yes >&5 > /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: > cannot find -lboost_python-yes > collect2: error: ld returned 1 exit status > > which makes me wonder if my copy of boost is broken or something?! I > am looking for a simple way to test it. Ok so I tried LDFLAGS=-L/usr/lib64 ./configure --without-libmodbus --with-realtime=uspace --with-python=/usr/bin/python2.7 --with-boost-python=py27 (all one line) and it still lands in the same failure. I attached the logfile Thanks for the persistence, Evan > >> >> On April 23, 2017 11:08:33 AM MDT, Evan Foss wrote: >>> >>> On Sun, Apr 23, 2017 at 2:55 PM, Sebastian Kuzminsky >>> wrote: On 04/22/2017 09:25 PM, Evan Foss wrote: > > On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminsky > wrote: From the configure --help output: >--with-boost-python Specify the boost python shared library > to use. For >instance, > --with-boost-python=boost_python-py25. >Defaults to boost-python. If you use this > then you >should probably set PYTHON too, to avoid > using >multiple python versions. >>> >>> I tried adding --with-boost-python=boost_python-py27 it didn't help. I've led you astray. But in my defense, that --help output led *me* astray. Our configure script actually wants just this: --with-boost-python=py27 Try that, and if it works like I think it will, I'll update the --help info. >>> >>> >>> I tried the following line. >>> ./configure --enable-non-distributable=yes --without-libmodbus >>> --prefix=/home/user1/programs/linuxcnc --with-realtime=uspace >>> --with-python=/usr/bin/python2.7 --with-boost-python=py27 >>> >>> and this is the end of the output. (config.log attached) >>> >>> checking for msgfmt... /usr/bin/msgfmt >>> checking for --tcl support in msgfmt... yes >>> checking for Python support... yes >>> checking python version... OK >>> checking version of python libraries... python2.7 >>> checking match between tk and Tkinter versions... 8.5 >>> checking location of Python header files... /usr/include/python2.7 >>> checking for Python headers... -I/usr/include/python2.7 >>> checking for Python libraries... -lpthread -ldl -lutil >>> checking whether the Boost::Python headers are available... yes >>> checking for boost::python shared library... >>> configure: error: boost::python is required to build LinuxCNC >>> >>> >>> -- Sebastian Kuzminsky Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot Emc-users mailing list
Re: [Emc-users] [emc-users] Building from source
On Sun, Apr 23, 2017 at 5:56 PM, Sebastian Kuzminskywrote: > This looks closer, the relevant part from the config.log is this: > > configure:8072: g++ -o conftest -g -O2 -std=c++11 -I/usr/include/python2.7 > conftest.cpp -lXinerama -lpython2.7 -lboost_python-py27 >&5 > /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: > cannot find -lboost_python-py27 collect2: error: ld returned 1 exit status > > So it's looking for the correct library name now, and you said earlier you > have it here: > > /usr/lib64/libboost_python-2.7.so Yep that file is there. > So try adding LDFLAGS=-L/usr/lib64, either as an environment variable or via > the configure flag. I tried this... ./configure --without-libmodbus --with-realtime=uspace --with-python=/usr/bin/python2.7 --with-boost-python LDFLAGS=-L/usr/lib/64 and later this for good measure... export LDFLAGS=-L/usr/lib64 Sadly I still get this... checking for xgettext tcl bug... xgettext version 0.19.7 OK checking for msgfmt... /usr/bin/msgfmt checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... 8.5 checking location of Python header files... /usr/include/python2.7 checking for Python headers... -I/usr/include/python2.7 checking for Python libraries... -lpthread -ldl -lutil checking whether the Boost::Python headers are available... yes checking for boost::python shared library... configure: error: boost::python is required to build LinuxCNC attached is the config.log based on what you said I found this configure:8072: g++ -o conftest -g -O2 -std=c++11 -I/usr/include/python2.7 -L/usr/lib/64 conftest.cpp -lXinerama -lpython2.7 -lboost_python-yes >&5 /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_python-yes collect2: error: ld returned 1 exit status which makes me wonder if my copy of boost is broken or something?! I am looking for a simple way to test it. > > On April 23, 2017 11:08:33 AM MDT, Evan Foss wrote: >> >> On Sun, Apr 23, 2017 at 2:55 PM, Sebastian Kuzminsky >> wrote: >>> >>> On 04/22/2017 09:25 PM, Evan Foss wrote: On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminsky wrote: >>> >>> From the configure --help output: >>> --with-boost-python Specify the boost python shared library to use. For instance, --with-boost-python=boost_python-py25. Defaults to boost-python. If you use this then you should probably set PYTHON too, to avoid using multiple python versions. >>> >>> >> >> I tried adding --with-boost-python=boost_python-py27 it didn't help. >>> >>> >>> I've led you astray. But in my defense, that --help output led *me* >>> astray. >>> >>> Our configure script actually wants just this: >>> >>> --with-boost-python=py27 >>> >>> Try that, and if it works like I think it will, I'll update the --help >>> info. >> >> >> I tried the following line. >> ./configure --enable-non-distributable=yes --without-libmodbus >> --prefix=/home/user1/programs/linuxcnc --with-realtime=uspace >> --with-python=/usr/bin/python2.7 --with-boost-python=py27 >> >> and this is the end of the output. (config.log attached) >> >> checking for msgfmt... /usr/bin/msgfmt >> checking for --tcl support in msgfmt... yes >> checking for Python support... yes >> checking python version... OK >> checking version of python libraries... python2.7 >> checking match between tk and Tkinter versions... 8.5 >> checking location of Python header files... /usr/include/python2.7 >> checking for Python headers... -I/usr/include/python2.7 >> checking for Python libraries... -lpthread -ldl -lutil >> checking whether the Boost::Python headers are available... yes >> checking for boost::python shared library... >> configure: error: boost::python is required to build LinuxCNC >> >> >> >>> -- >>> Sebastian Kuzminsky >>> >>> >>> >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> >>> >>> Emc-users mailing list >>> Emc-users@lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/emc-users >> >> >> > > -- > Sebastian Kuzminsky -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd
Re: [Emc-users] [emc-users] Building from source
This looks closer, the relevant part from the config.log is this: configure:8072: g++ -o conftest -g -O2 -std=c++11 -I/usr/include/python2.7 conftest.cpp -lXinerama -lpython2.7 -lboost_python-py27 >&5 /usr/lib/gcc/x86_64-pc-linux-gnu/4.7.3/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_python-py27 collect2: error: ld returned 1 exit status So it's looking for the correct library name now, and you said earlier you have it here: /usr/lib64/libboost_python-2.7.so So try adding LDFLAGS=-L/usr/lib64, either as an environment variable or via the configure flag. On April 23, 2017 11:08:33 AM MDT, Evan Fosswrote: >On Sun, Apr 23, 2017 at 2:55 PM, Sebastian Kuzminsky >wrote: >> On 04/22/2017 09:25 PM, Evan Foss wrote: >>> On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminsky > wrote: >> From the configure --help output: >> >>> --with-boost-python Specify the boost python shared >library to use. For >>> instance, >--with-boost-python=boost_python-py25. >>> Defaults to boost-python. If you use >this then you >>> should probably set PYTHON too, to >avoid using >>> multiple python versions. >> > > I tried adding --with-boost-python=boost_python-py27 it didn't >help. >> >> I've led you astray. But in my defense, that --help output led *me* >astray. >> >> Our configure script actually wants just this: >> >> --with-boost-python=py27 >> >> Try that, and if it works like I think it will, I'll update the >--help info. > >I tried the following line. >./configure --enable-non-distributable=yes --without-libmodbus >--prefix=/home/user1/programs/linuxcnc --with-realtime=uspace >--with-python=/usr/bin/python2.7 --with-boost-python=py27 > >and this is the end of the output. (config.log attached) > >checking for msgfmt... /usr/bin/msgfmt >checking for --tcl support in msgfmt... yes >checking for Python support... yes >checking python version... OK >checking version of python libraries... python2.7 >checking match between tk and Tkinter versions... 8.5 >checking location of Python header files... /usr/include/python2.7 >checking for Python headers... -I/usr/include/python2.7 >checking for Python libraries... -lpthread -ldl -lutil >checking whether the Boost::Python headers are available... yes >checking for boost::python shared library... >configure: error: boost::python is required to build LinuxCNC > > > >> -- >> Sebastian Kuzminsky >> >> >-- >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> ___ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users > > > >-- >Home >http://evanfoss.googlepages.com/ >Work >http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ > >-BEGIN PGP PUBLIC KEY BLOCK- >Version: GnuPG v2 > >mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai >VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd >hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE >JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 >stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go >bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp >cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC >ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN >bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X >tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj >XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 >APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ >3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC >qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 >SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M >K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 >A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk >5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ >xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er >ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 >Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 >0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D >gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 >CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD >fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 >EY347EidAw== >=Ta4p >-END PGP PUBLIC KEY BLOCK- -- Sebastian Kuzminsky -- Check out the vibrant
Re: [Emc-users] [emc-users] Building from source
On Sun, Apr 23, 2017 at 2:55 PM, Sebastian Kuzminskywrote: > On 04/22/2017 09:25 PM, Evan Foss wrote: >> On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminsky >> wrote: > From the configure --help output: > >> --with-boost-python Specify the boost python shared library to >> use. For >> instance, >> --with-boost-python=boost_python-py25. >> Defaults to boost-python. If you use this then >> you >> should probably set PYTHON too, to avoid using >> multiple python versions. > I tried adding --with-boost-python=boost_python-py27 it didn't help. > > I've led you astray. But in my defense, that --help output led *me* astray. > > Our configure script actually wants just this: > > --with-boost-python=py27 > > Try that, and if it works like I think it will, I'll update the --help info. I tried the following line. ./configure --enable-non-distributable=yes --without-libmodbus --prefix=/home/user1/programs/linuxcnc --with-realtime=uspace --with-python=/usr/bin/python2.7 --with-boost-python=py27 and this is the end of the output. (config.log attached) checking for msgfmt... /usr/bin/msgfmt checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... 8.5 checking location of Python header files... /usr/include/python2.7 checking for Python headers... -I/usr/include/python2.7 checking for Python libraries... -lpthread -ldl -lutil checking whether the Boost::Python headers are available... yes checking for boost::python shared library... configure: error: boost::python is required to build LinuxCNC > -- > Sebastian Kuzminsky > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -END PGP PUBLIC KEY BLOCK- This file contains any messages produced by compilers while running configure, to aid debugging if configure makes a mistake. It was created by LinuxCNC configure 2.7.0, which was generated by GNU Autoconf 2.69. Invocation command line was $ ./configure --enable-non-distributable=yes --without-libmodbus --prefix=/home/user1/programs/linuxcnc --with-realtime=uspace --with-python=/usr/bin/python2.7 --with-boost-python=py27 ## - ## ## Platform. ## ## - ## hostname = turingatlarge uname -m = x86_64 uname -r = 4.9.16-gentoo uname -s = Linux uname -v = #2 SMP Sun Apr 2 02:22:32 UTC 2017 /usr/bin/uname -p = Intel(R) Core(TM) i7-3720QM CPU @ 2.60GHz /bin/uname -X = unknown /bin/arch = unknown /usr/bin/arch -k = unknown /usr/convex/getsysinfo = unknown /usr/bin/hostinfo = unknown /bin/machine =
Re: [Emc-users] [emc-users] Building from source
On 04/22/2017 09:25 PM, Evan Foss wrote: > On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminskywrote: From the configure --help output: > --with-boost-python Specify the boost python shared library to use. > For > instance, --with-boost-python=boost_python-py25. > Defaults to boost-python. If you use this then > you > should probably set PYTHON too, to avoid using > multiple python versions. >>> >>> I tried adding --with-boost-python=boost_python-py27 it didn't help. I've led you astray. But in my defense, that --help output led *me* astray. Our configure script actually wants just this: --with-boost-python=py27 Try that, and if it works like I think it will, I'll update the --help info. -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sat, Apr 22, 2017 at 1:56 PM, Sebastian Kuzminskywrote: > On 04/21/2017 10:37 PM, Evan Foss wrote: >> On Fri, Apr 21, 2017 at 8:14 PM, Sebastian Kuzminsky >> wrote: >>> On 04/21/2017 01:15 PM, Evan Foss wrote: The basics * I am running Gentoo Linux (so it's non-debian) * Yes I have the development headers installed. Gentoo by design requires them. Attached is a file called python-boost.text which includes all the files in /usr/include/boost/python This is the package I used to install boost dev-util/boost-build-1.62.0-r1::gentoo USE="python -examples {-test}" PYTHON_TARGETS="python2_7" * Yes I have python (the following revisions are installed 2.7.12, 3.3.5-r3, and 3.4.5). I am only trying to point it at 2.7.12 This is how I am trying to configure it. ./configure --without-libmodbus --with-realtime=uspace --with-python=/usr/bin/python2.7 --prefix=/home/user1/programs/linuxcnc and the following is tail of that output hecking for xgettext tcl bug... xgettext version 0.19.7 OK checking for msgfmt... /usr/bin/msgfmt checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... 8.5 checking location of Python header files... /usr/include/python2.7 checking for Python headers... -I/usr/include/python2.7 checking for Python libraries... -lpthread -ldl -lutil checking whether the Boost::Python headers are available... yes checking for boost::python shared library... configure: error: boost::python is required to build LinuxCNC Is there some way to point configure at the location where boost is installed? >>> >>> Hi Evan! >>> >>> From the configure --help output: >>> --with-boost-python Specify the boost python shared library to use. For instance, --with-boost-python=boost_python-py25. Defaults to boost-python. If you use this then you should probably set PYTHON too, to avoid using multiple python versions. >>> >> >> I tried adding --with-boost-python=boost_python-py27 it didn't help. >> >>> If your boost-python library is in an unusual directory you'll probably >>> have to set it with -L in LDFLAGS. >> >> I tried pointing -L at the location of the compiled library, and out >> of desperation i tried pointing it at the headers. >> >> What versions of python and boost::python are required to build linuxcnc? > > LinuxCNC is fairly version-insensitive with boost-python. It works with > *at least* 1.48 (on Ubuntu Precise), 1.48 (Debian Wheezy), 1.55 (Debian > Jessie), and 1.62 (Debian Stretch pre-release), and probably all the > ones in between, and probably some more besides. Ok so that isn't the problem. > What is the full path to your libboost_python-py2.7.so? I looked for libboost_python and found the following files. Gentoo supports this thing called slots which lets you install multiple package revisions but build software to only use a specific version. /usr/lib64/libboost_python-3.4.so.1.56.0 /usr/lib64/libboost_python-3.4.so /usr/lib64/libboost_python-2.7.so /usr/lib64/debug/usr/lib64/libboost_python-3.4.so.1.56.0.debug /usr/lib64/debug/usr/lib64/libboost_python-2.7.so.1.56.0.debug /usr/lib64/libboost_python-2.7.so.1.56.0 /usr/lib64/libboost_python-2.7-mt.so /usr/lib64/libboost_python-3.4-mt.so > What did you set LDFLAGS to? I started with LDFLAGS="-L/usr/lib64" LDFLAGS="-L/usr/lib" then i got desperate and tried... LDFLAGS="-L/usr/include/boost/python" LDFLAGS="-L/usr/include/" LDFLAGS="-L/usr/bin" > What does the boost-python part of your config.log say after configure > fails? I attached the full log but I think this is the line you are talking about. Sorry I meant to include this in the first email. BOOST_PYTHON_LIBS='' Thank you, Evan > > -- > Sebastian Kuzminsky > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1
Re: [Emc-users] [emc-users] Building from source
On 04/21/2017 10:37 PM, Evan Foss wrote: > On Fri, Apr 21, 2017 at 8:14 PM, Sebastian Kuzminskywrote: >> On 04/21/2017 01:15 PM, Evan Foss wrote: >>> The basics >>> * I am running Gentoo Linux (so it's non-debian) >>> * Yes I have the development headers installed. Gentoo by design >>> requires them. Attached is a file called python-boost.text which >>> includes all the files in /usr/include/boost/python >>> This is the package I used to install boost >>> dev-util/boost-build-1.62.0-r1::gentoo USE="python -examples {-test}" >>> PYTHON_TARGETS="python2_7" >>> * Yes I have python (the following revisions are installed 2.7.12, >>> 3.3.5-r3, and 3.4.5). I am only trying to point it at 2.7.12 >>> >>> This is how I am trying to configure it. >>> ./configure --without-libmodbus --with-realtime=uspace >>> --with-python=/usr/bin/python2.7 >>> --prefix=/home/user1/programs/linuxcnc >>> >>> and the following is tail of that output >>> >>> hecking for xgettext tcl bug... xgettext version 0.19.7 OK >>> checking for msgfmt... /usr/bin/msgfmt >>> checking for --tcl support in msgfmt... yes >>> checking for Python support... yes >>> checking python version... OK >>> checking version of python libraries... python2.7 >>> checking match between tk and Tkinter versions... 8.5 >>> checking location of Python header files... /usr/include/python2.7 >>> checking for Python headers... -I/usr/include/python2.7 >>> checking for Python libraries... -lpthread -ldl -lutil >>> checking whether the Boost::Python headers are available... yes >>> checking for boost::python shared library... >>> configure: error: boost::python is required to build LinuxCNC >>> >>> Is there some way to point configure at the location where boost is >>> installed? >> >> Hi Evan! >> >> From the configure --help output: >> >>> --with-boost-python Specify the boost python shared library to use. >>> For >>> instance, --with-boost-python=boost_python-py25. >>> Defaults to boost-python. If you use this then you >>> should probably set PYTHON too, to avoid using >>> multiple python versions. >> > > I tried adding --with-boost-python=boost_python-py27 it didn't help. > >> If your boost-python library is in an unusual directory you'll probably >> have to set it with -L in LDFLAGS. > > I tried pointing -L at the location of the compiled library, and out > of desperation i tried pointing it at the headers. > > What versions of python and boost::python are required to build linuxcnc? LinuxCNC is fairly version-insensitive with boost-python. It works with *at least* 1.48 (on Ubuntu Precise), 1.48 (Debian Wheezy), 1.55 (Debian Jessie), and 1.62 (Debian Stretch pre-release), and probably all the ones in between, and probably some more besides. What is the full path to your libboost_python-py2.7.so? What did you set LDFLAGS to? What does the boost-python part of your config.log say after configure fails? -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Fri, Apr 21, 2017 at 8:14 PM, Sebastian Kuzminskywrote: > On 04/21/2017 01:15 PM, Evan Foss wrote: >> The basics >> * I am running Gentoo Linux (so it's non-debian) >> * Yes I have the development headers installed. Gentoo by design >> requires them. Attached is a file called python-boost.text which >> includes all the files in /usr/include/boost/python >> This is the package I used to install boost >> dev-util/boost-build-1.62.0-r1::gentoo USE="python -examples {-test}" >> PYTHON_TARGETS="python2_7" >> * Yes I have python (the following revisions are installed 2.7.12, >> 3.3.5-r3, and 3.4.5). I am only trying to point it at 2.7.12 >> >> This is how I am trying to configure it. >> ./configure --without-libmodbus --with-realtime=uspace >> --with-python=/usr/bin/python2.7 >> --prefix=/home/user1/programs/linuxcnc >> >> and the following is tail of that output >> >> hecking for xgettext tcl bug... xgettext version 0.19.7 OK >> checking for msgfmt... /usr/bin/msgfmt >> checking for --tcl support in msgfmt... yes >> checking for Python support... yes >> checking python version... OK >> checking version of python libraries... python2.7 >> checking match between tk and Tkinter versions... 8.5 >> checking location of Python header files... /usr/include/python2.7 >> checking for Python headers... -I/usr/include/python2.7 >> checking for Python libraries... -lpthread -ldl -lutil >> checking whether the Boost::Python headers are available... yes >> checking for boost::python shared library... >> configure: error: boost::python is required to build LinuxCNC >> >> Is there some way to point configure at the location where boost is >> installed? > > Hi Evan! > > From the configure --help output: > >> --with-boost-python Specify the boost python shared library to use. For >> instance, --with-boost-python=boost_python-py25. >> Defaults to boost-python. If you use this then you >> should probably set PYTHON too, to avoid using >> multiple python versions. > I tried adding --with-boost-python=boost_python-py27 it didn't help. > If your boost-python library is in an unusual directory you'll probably > have to set it with -L in LDFLAGS. I tried pointing -L at the location of the compiled library, and out of desperation i tried pointing it at the headers. What versions of python and boost::python are required to build linuxcnc? > -- > Sebastian Kuzminsky > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -BEGIN PGP PUBLIC KEY BLOCK- Version: GnuPG v2 mQENBFYy4RYBCAC183JomLtbdAlcKiaPDoVHq52LDmVmH75aiEc69m7YxDt54/ai VtYCAobbGVIyn3Hlz3uhF6LnPl/6Lm1VdnCfpwu3KQhCO6ds10ow2C30X4ohCqOd hCVg5C+ILmQkEffFrFODy3ji+PYTF4pADvHCWsTMv0hf0llwFOJsBCK6cl02IffE JPqy4PjM1nZ9HpzT84JBaG/4OGvTZ8SQ2yFUl265jagvygPTf88H1xpZHH1r8dB1 stjUHLmPH8AOyDgKxFchgGeDc3p/vJtgDDIXAFfDXG0NSRovLmtaQdGxe47Zf/go bXiEM7YL2WqQe5zfEA919JxkEwlDKYniOSVzABEBAAG0N0V2YW4gRm9zcyAoVGhp cyBpcyBteSBwdWJsaWMga2V5LikgPGV2YW5mb3NzQGdtYWlsLmNvbT6JATkEEwEC ACMFAlYy4RYCGwMHCwkIBwMCAQYVCAIJCgsEFgIDAQIeAQIXgAAKCRCIpQTcE8nN bbBaCACAm8pU5lG1ev2Fsw68Axtcl57SJrYieqX96c3YuYH9JpqMqJRnd9nDKw9X tQuvuH7tUk0VbOaDqReOYJVI/4c5wb9AaOFp6K2DUcupq6XhgXpvz3HzoPwjAdIj XuQzdRUx5+innTJrSkGuBYW/CZ2zqEx4xfLlq4rO0hoTUMR8QVp2cCrkw6BT0m86 APIw/ZnjoxM8IEzr7MxfRIg3qpzrZk28rmhx+k78Jyk61UhwcCPGIm/pjUopTwYJ 3YBdRB2cYD2aN7A1JVf5cRmSQYooHBGpH0kYvomGk97PKqypVuJ7OpG9xM58wUcC qUVt9hKlePLzP8csYjt8onqI7qIIuQENBFYy4RYBCADlH8spG3WkCx62vB5mr5Z0 SCDd/RcyA4A5y5EOj5KurQkrSWpgi9Ho1yKruMJ6blQR2qkc66KqH9pnXDm/ZI1M K/wdW3ngETxBmXoozzFMT89aEWIVR5/PFodWK1elekE9iJxACuR98Zg2QttTD3x8 A9w8VEyMLOXcDTrPFpHegMKswFBg5iuMulAdXAoGejWTI3n+qKFpabHm2Lfs6wjk 5rjucpTdeFK6UeWF1xAvNxXibuu5BlGwv53930qIXRwO/Gn2Rh5DXWxKU2fEIme/ xgQQmIsDeUoWbfybdjw/x7Q0LW4mINiLDQcGHHRQKFIxbAJCT3USPLGh5xwE9/Er ABEBAAGJAR8EGAECAAkFAlYy4RYCGwwACgkQiKUE3BPJzW0uYAf9Hf30n8tM3mR2 Zo6ESE0ivgdgjaJtAWrBUx7JzAzPjBnBOlNnu5Y9lVEqetvUPH6e3PvaHYUuaUU8 0HwxuKBW9nUprgV6uIu1DZmlcp+SxpbuCy7RDpNocRLNWWFMaYYzznmTgfnTgD4D gCq8Mf1mcfrluTkOAo+QNqbMfl1GISClopRqxVuAo59ewgMnFujwgd8w12BwWl24 CzqOs5HqcUslePj+LzcjSNgVCklYwKl+0dsb/fctMOCtHodwqm2CBJ+zydvNmYkD fxda/J91Z1xrah5ec++FL0L4vs+jCiIWJeupJFKlr1hCMZiiGH7W554loK5l4jv3 EY347EidAw== =Ta4p -END PGP PUBLIC KEY BLOCK- -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___
Re: [Emc-users] [emc-users] Building from source
On 04/21/2017 01:15 PM, Evan Foss wrote: > The basics > * I am running Gentoo Linux (so it's non-debian) > * Yes I have the development headers installed. Gentoo by design > requires them. Attached is a file called python-boost.text which > includes all the files in /usr/include/boost/python > This is the package I used to install boost > dev-util/boost-build-1.62.0-r1::gentoo USE="python -examples {-test}" > PYTHON_TARGETS="python2_7" > * Yes I have python (the following revisions are installed 2.7.12, > 3.3.5-r3, and 3.4.5). I am only trying to point it at 2.7.12 > > This is how I am trying to configure it. > ./configure --without-libmodbus --with-realtime=uspace > --with-python=/usr/bin/python2.7 > --prefix=/home/user1/programs/linuxcnc > > and the following is tail of that output > > hecking for xgettext tcl bug... xgettext version 0.19.7 OK > checking for msgfmt... /usr/bin/msgfmt > checking for --tcl support in msgfmt... yes > checking for Python support... yes > checking python version... OK > checking version of python libraries... python2.7 > checking match between tk and Tkinter versions... 8.5 > checking location of Python header files... /usr/include/python2.7 > checking for Python headers... -I/usr/include/python2.7 > checking for Python libraries... -lpthread -ldl -lutil > checking whether the Boost::Python headers are available... yes > checking for boost::python shared library... > configure: error: boost::python is required to build LinuxCNC > > Is there some way to point configure at the location where boost is installed? Hi Evan! From the configure --help output: > --with-boost-python Specify the boost python shared library to use. For > instance, --with-boost-python=boost_python-py25. > Defaults to boost-python. If you use this then you > should probably set PYTHON too, to avoid using > multiple python versions. If your boost-python library is in an unusual directory you'll probably have to set it with -L in LDFLAGS. -- Sebastian Kuzminsky -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
[Emc-users] [emc-users] Building from source
Hi LinuxCNC, I am having trouble building from source. I am just trying to build the simulator to test some things. I am a developer on an open source pcb layout program and I need to work on g-code. I also want to use cutsim (https://github.com/aewallin/cutsim) and I need linuxcnc to build for that to happen. The basics * I am running Gentoo Linux (so it's non-debian) * Yes I have the development headers installed. Gentoo by design requires them. Attached is a file called python-boost.text which includes all the files in /usr/include/boost/python This is the package I used to install boost dev-util/boost-build-1.62.0-r1::gentoo USE="python -examples {-test}" PYTHON_TARGETS="python2_7" * Yes I have python (the following revisions are installed 2.7.12, 3.3.5-r3, and 3.4.5). I am only trying to point it at 2.7.12 This is how I am trying to configure it. ./configure --without-libmodbus --with-realtime=uspace --with-python=/usr/bin/python2.7 --prefix=/home/user1/programs/linuxcnc and the following is tail of that output hecking for xgettext tcl bug... xgettext version 0.19.7 OK checking for msgfmt... /usr/bin/msgfmt checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... 8.5 checking location of Python header files... /usr/include/python2.7 checking for Python headers... -I/usr/include/python2.7 checking for Python libraries... -lpthread -ldl -lutil checking whether the Boost::Python headers are available... yes checking for boost::python shared library... configure: error: boost::python is required to build LinuxCNC Is there some way to point configure at the location where boost is installed? Thanks, Evan Foss -- Home http://evanfoss.googlepages.com/ Work http://www.masseyeandear.org/research/otolaryngology/investigators/laboratories/eaton-peabody-laboratories/epl-engineering-resources/epl-engineering-staff //usr/include/boost/python/ //usr/include/boost/python/cast.hpp //usr/include/boost/python/object //usr/include/boost/python/object/py_function.hpp //usr/include/boost/python/object/enum_base.hpp //usr/include/boost/python/object/make_ptr_instance.hpp //usr/include/boost/python/object/stl_iterator_core.hpp //usr/include/boost/python/object/iterator_core.hpp //usr/include/boost/python/object/add_to_namespace.hpp //usr/include/boost/python/object/inheritance.hpp //usr/include/boost/python/object/instance.hpp //usr/include/boost/python/object/class.hpp //usr/include/boost/python/object/value_holder.hpp //usr/include/boost/python/object/make_holder.hpp //usr/include/boost/python/object/find_instance.hpp //usr/include/boost/python/object/inheritance_query.hpp //usr/include/boost/python/object/function_handle.hpp //usr/include/boost/python/object/life_support.hpp //usr/include/boost/python/object/class_detail.hpp //usr/include/boost/python/object/function.hpp //usr/include/boost/python/object/forward.hpp //usr/include/boost/python/object/function_doc_signature.hpp //usr/include/boost/python/object/function_object.hpp //usr/include/boost/python/object/pickle_support.hpp //usr/include/boost/python/object/value_holder_fwd.hpp //usr/include/boost/python/object/class_metadata.hpp //usr/include/boost/python/object/make_instance.hpp //usr/include/boost/python/object/iterator.hpp //usr/include/boost/python/object/class_wrapper.hpp //usr/include/boost/python/object/pointer_holder.hpp //usr/include/boost/python/converter //usr/include/boost/python/converter/builtin_converters.hpp //usr/include/boost/python/converter/pyobject_type.hpp //usr/include/boost/python/converter/context_result_converter.hpp //usr/include/boost/python/converter/arg_from_python.hpp //usr/include/boost/python/converter/return_from_python.hpp //usr/include/boost/python/converter/shared_ptr_to_python.hpp //usr/include/boost/python/converter/registered.hpp //usr/include/boost/python/converter/shared_ptr_from_python.hpp //usr/include/boost/python/converter/registrations.hpp //usr/include/boost/python/converter/implicit.hpp //usr/include/boost/python/converter/to_python_function_type.hpp //usr/include/boost/python/converter/pytype_object_mgr_traits.hpp //usr/include/boost/python/converter/rvalue_from_python_data.hpp //usr/include/boost/python/converter/object_manager.hpp //usr/include/boost/python/converter/from_python.hpp //usr/include/boost/python/converter/arg_to_python_base.hpp //usr/include/boost/python/converter/pointer_type_id.hpp //usr/include/boost/python/converter/shared_ptr_deleter.hpp //usr/include/boost/python/converter/arg_to_python.hpp //usr/include/boost/python/converter/obj_mgr_arg_from_python.hpp //usr/include/boost/python/converter/registered_pointee.hpp //usr/include/boost/python/converter/pyobject_traits.hpp //usr/include/boost/python/converter/registry.hpp //usr/include/boost/python/converter/constructor_function.hpp
Re: [Emc-users] [emc-users] Building from source
On Fri, Oct 2, 2015 at 12:01 AM, MC Casonwrote: > >You need the development files for boost::python. Using `aptitude > search boost` will show you what files you need. I am running gentoo so it is emerge --search boost only I already have boost so I get. I have already installed dev-libs/boost dev-util/boost-build sys-devel/boost-m4 There is no -dev package headers are installed because gentoo is source based every package is compiled on install. >This should get you what you need: > sudo apt-get install libboost-python-dev I did an emerge of dev-libs/boost with python headers. > >> Ok I took this to mean --disable-python your ./configure has to be >> broken and tried to build it with python. It complained about not >> having tk support in python so I recompiled python and then everything >> that required it. Not fun. >> >> For my trouble I now have the same issue using --disable-python flag. >> With out that flag I get another issue. This is the end of my config >> >> checking for msgfmt... /usr/bin/msgfmt >> checking for --tcl support in msgfmt... yes >> checking for Python support... yes >> checking python version... OK >> checking version of python libraries... python2.7 >> checking match between tk and Tkinter versions... 8.5 >> checking location of Python header files... /usr/include/python2.7 >> checking for Python headers... -I/usr/include/python2.7 >> checking for Python libraries... -lpthread -ldl -lutil >> checking whether the Boost::Python headers are available... yes >> checking for boost::python shared library... >> configure: error: boost::python is required to build LinuxCNC >> >> What package is boost::python from? I am not a python guy. >> > > -- > MC Cason > Eagle3D - Created by Matthias Weißer > github.com/mcason/Eagle3D > > > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 1:14 PM, Jeff Eplerwrote: > On Sun, Sep 20, 2015 at 03:40:39AM +, Evan Foss wrote: >> On Sun, Sep 20, 2015 at 2:35 AM, Jeff Epler wrote: >> > It looks like you're missing some python-related packages, namely the >> > one that provides pyconfig.h and the one that provides _tkinter.so. >> >> Yes I got that far. Why does the compile bomb when I try to build with >> out python? > > As far as I'm aware, python and boost-python development headers are > currently required to build linuxcnc. Once again, I'll review patches > with the goal of making these items optional (in fact I'd personally > like boost-python to be optional, because the way it is used in the > interpreter to support the "remapping" feature I don't use adds a lot of > compile time) Ok I took this to mean --disable-python your ./configure has to be broken and tried to build it with python. It complained about not having tk support in python so I recompiled python and then everything that required it. Not fun. For my trouble I now have the same issue using --disable-python flag. With out that flag I get another issue. This is the end of my config checking for msgfmt... /usr/bin/msgfmt checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... 8.5 checking location of Python header files... /usr/include/python2.7 checking for Python headers... -I/usr/include/python2.7 checking for Python libraries... -lpthread -ldl -lutil checking whether the Boost::Python headers are available... yes checking for boost::python shared library... configure: error: boost::python is required to build LinuxCNC What package is boost::python from? I am not a python guy. > Jeff > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
You need the development files for boost::python. Using `aptitude search boost` will show you what files you need. This should get you what you need: sudo apt-get install libboost-python-dev > Ok I took this to mean --disable-python your ./configure has to be > broken and tried to build it with python. It complained about not > having tk support in python so I recompiled python and then everything > that required it. Not fun. > > For my trouble I now have the same issue using --disable-python flag. > With out that flag I get another issue. This is the end of my config > > checking for msgfmt... /usr/bin/msgfmt > checking for --tcl support in msgfmt... yes > checking for Python support... yes > checking python version... OK > checking version of python libraries... python2.7 > checking match between tk and Tkinter versions... 8.5 > checking location of Python header files... /usr/include/python2.7 > checking for Python headers... -I/usr/include/python2.7 > checking for Python libraries... -lpthread -ldl -lutil > checking whether the Boost::Python headers are available... yes > checking for boost::python shared library... > configure: error: boost::python is required to build LinuxCNC > > What package is boost::python from? I am not a python guy. > -- MC Cason Eagle3D - Created by Matthias Weißer github.com/mcason/Eagle3D -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On 20/09/15 04:58, Sebastian Kuzminsky wrote: > Ah, you're building on Gentoo, I didn't realize that. We do not > currently have instructions for how to build on Gentoo, unfortunately. > LinuxCNC currently targets/supports Debian and Debian-derived > distributions like Ubuntu. There have been some efforts to develop the > Gentoo build documentation, but as far as I know they have not produced > any results yet. If you get your Gentoo build to work, I'd welcome an > ebuild file and/or documentation. > > You're right that src/configure is supposed to identify missing build > dependencies. If it fails at that job, that's a bug, and we'd love a patch. > > debian/configure and dpkg-checkbuilddeps are Debian-specific tools that > do a similar but different job - they tell you, in a programmatic way, > which debian packages are missing and need to be installed in order to > build. It is nowadays irritating that distributions made their own decisions on 'improvements' in the past. So Linux has a well deserved reputation for being 'painful to work with'. I've worked with SUSE Linux for so many years now that when I've come across sites using something else those little differences cause hours of head scratching on things 'that should just work'. Add in problems like Python2 vs Python3 and even 64bit vs 32bit and it does become something of a nightmare? :( A debate on 'cross platform' working should perhaps start with 'cross distribution' working. I've just finished upgrading the 'old' development machine from SUSE13.1 to SUSE 'Tumbleweed' since many of the nice new tools like FreeCAD and KiCAD will not load current versions on even SUSE13.2, remaining with older versions with known bugs. Start throwing complete new processor families into the mix such as the various ARM variants and its a wonder anything ever works? -- Lester Caine - G8HFL - Contact - http://lsces.co.uk/wiki/?page=contact L.S.Caine Electronic Services - http://lsces.co.uk EnquirySolve - http://enquirysolve.com/ Model Engineers Digital Workshop - http://medw.co.uk Rainbow Digital Media - http://rainbowdigitalmedia.co.uk -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 03:40:39AM +, Evan Foss wrote: > On Sun, Sep 20, 2015 at 2:35 AM, Jeff Eplerwrote: > > It looks like you're missing some python-related packages, namely the > > one that provides pyconfig.h and the one that provides _tkinter.so. > > Yes I got that far. Why does the compile bomb when I try to build with > out python? As far as I'm aware, python and boost-python development headers are currently required to build linuxcnc. Once again, I'll review patches with the goal of making these items optional (in fact I'd personally like boost-python to be optional, because the way it is used in the interpreter to support the "remapping" feature I don't use adds a lot of compile time) Jeff -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On 09/19/2015 07:00 PM, Evan Foss wrote: > Hi Folks, > > I am trying to build from source. I know this is not advised but I am > working on debugging a gcode generator and I just want the simulator > to run on my regular desktop. > > > Compiling emc/task/emctask.cc > In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, > from /usr/include/boost/python/args.hpp:8, > from /usr/include/boost/python.hpp:11, > from emc/rs274ngc/interp_internal.hh:16, > from emc/rs274ngc/rs274ngc_interp.hh:20, > from emc/task/emctask.cc:29: > /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: > pyconfig.h: No such file or directory > compilation terminated. > Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed > make: *** [objects/emc/task/emctask.o] Error 1 Hi Evan, unfortunately our build documentation is not super easy to find. LinuxCNC has many build dependencies. They are recorded in the debian/configure script. Instructions on how to use it to discover what you need to install are here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies -- Sebastian Kuzminsky -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
Apologies for my reply. I was the stupid human posing the question. When I read you only wanted the simulator, I thought I would ask why not just run in a VM, but, I didn't ask in a text friendly way. On Sat, Sep 19, 2015, 10:38 PM Jeff Eplerwrote: > It looks like you're missing some python-related packages, namely the > one that provides pyconfig.h and the one that provides _tkinter.so. > > On my Debian Jessie system the relevant packages seem to be > libpython2.7-dev: /usr/include/python2.7/pyconfig.h > python-tk: /usr/lib/python2.7/lib-dynload/_tkinter.so > but different OSes and releases may have different package names. > > I will happily review a patch to detect this in configure and give a > more useful error message. > > Jeff > > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 2:35 AM, Jeff Eplerwrote: > It looks like you're missing some python-related packages, namely the > one that provides pyconfig.h and the one that provides _tkinter.so. Yes I got that far. Why does the compile bomb when I try to build with out python? > On my Debian Jessie system the relevant packages seem to be > libpython2.7-dev: /usr/include/python2.7/pyconfig.h > python-tk: /usr/lib/python2.7/lib-dynload/_tkinter.so > but different OSes and releases may have different package names. I am running gentoo, the -r1 figures on the end of the packages are just releases of the ebuilds to install them. dev-lang/python-3.4.1 dev-lang/python-3.3.5-r1 dev-lang/python-2.7.7 Boost was built with out python support. dev-util/boost-build-1.56.0 dev-libs/boost-1.56.0-r1:0/1.56.0 (The double version number is because I have it installed in two slots. One for each python 3.4.1 and one for 2.7.7) src $ ./configure --enable-simulator --without-libmodbus --with-tkConfig=/usr/lib64/tkConfig.sh --with-tclconfig=/usr/lib64/tclConfig.sh configure: WARNING: unrecognized options: --with-tclconfig checking build toplevel... /home/user1/Documents/build/linuxcnc-a5a1937 checking installation prefix... run in place checking for grep... /bin/grep checking for egrep... /bin/egrep checking for RT dir... configure: WARNING: --enable-simulator is deprecated. Use --with-realtime=uspace instead. Using userspace realtime checking whether to enable userspace PCI access... yes checking for libudev... yes - version 216 checking for cc version... not specified checking for gcc... gcc checking whether the C compiler works... yes checking for C compiler default output file name... a.out checking for suffix of executables... checking whether we are cross compiling... no checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for usability of rdtscll from asm/msr.h... no checking for usability of linux/hidraw.h... yes checking for libusb-1.0... yes checking for module installation directory... configuring for run-in-place /home/user1/Documents/build/linuxcnc-a5a1937/rtlib checking for glib... yes - 2.42.2 checking for GTK 2.4.0 or above... yes - 2.24.24 checking for libgnomeprintui-2.2... no -- printing from classicladder will not be possible checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking whether g++ supports C++11 features by default... no checking whether g++ supports C++11 features with -std=c++11... yes checking whether make sets $(MAKE)... yes checking for ranlib... ranlib checking for ar... /usr/bin/ar checking for install... /usr/bin/install checking for sed... /bin/sed checking for ps... /bin/ps checking for kill... /bin/kill checking for whoami... /usr/bin/whoami checking for awk... /usr/bin/awk checking for insmod... /sbin/insmod checking for rmmod... /sbin/rmmod checking for lsmod... /bin/lsmod checking for pidof... /bin/pidof checking for ipcs... /usr/bin/ipcs checking for fuser... /bin/fuser checking for mandb... /usr/bin/mandb checking for python... /usr/bin/python checking whether to build documentation... no checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... (cached) /bin/egrep checking for ANSI C header files... yes checking for sys/wait.h that is POSIX.1 compatible... yes checking for semtimedop... yes checking for sincos function... yes checking for __sincos... no checking for tcl... /usr/lib64/tclConfig.sh found checking for tk... /usr/lib64/tkConfig.sh found checking whether to check for runtime dependencies... yes checking for BWidget using /usr/bin/tclsh8.5... found checking for BLT using tclsh8.5... found checking for img::png using /usr/bin/tclsh8.5... found checking for tclX using /usr/bin/tclsh8.5... found checking for X... libraries , headers checking for gethostbyname... yes checking for connect... yes checking for remove... yes checking for shmat... yes checking for IceConnectionNumber in -lICE... yes checking X11/extensions/Xinerama.h usability... yes checking X11/extensions/Xinerama.h presence... yes checking for X11/extensions/Xinerama.h... yes checking for XineramaQueryExtension in -lXinerama... yes checking for X11/Xaw/XawInit.h... yes checking for XawDialogGetValueString in -lXaw... yes checking readline/readline.h usability... yes checking readline/readline.h presence... yes checking for readline/readline.h... yes checking readline/history.h usability... yes checking readline/history.h presence... yes checking for readline/history.h... yes Trying readline without -ltermcap checking for readline in -lreadline... yes Trying readline with -ltermcap checking for readline in -lreadline... no Readline does not require -ltermcap checking
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 3:29 AM, Evan Fosswrote: > On Sun, Sep 20, 2015 at 3:20 AM, Sebastian Kuzminsky wrote: >> On 09/19/2015 07:00 PM, Evan Foss wrote: >>> Hi Folks, >>> >>> I am trying to build from source. I know this is not advised but I am >>> working on debugging a gcode generator and I just want the simulator >>> to run on my regular desktop. >>> >>> >>> Compiling emc/task/emctask.cc >>> In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, >>> from /usr/include/boost/python/args.hpp:8, >>> from /usr/include/boost/python.hpp:11, >>> from emc/rs274ngc/interp_internal.hh:16, >>> from emc/rs274ngc/rs274ngc_interp.hh:20, >>> from emc/task/emctask.cc:29: >>> /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: >>> pyconfig.h: No such file or directory >>> compilation terminated. >>> Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed >>> make: *** [objects/emc/task/emctask.o] Error 1 >> >> Hi Evan, unfortunately our build documentation is not super easy to >> find. LinuxCNC has many build dependencies. They are recorded in the >> debian/configure script. Instructions on how to use it to discover what >> you need to install are here: >> >> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies > > Yes I tried that. > cd debian > ./configure -a (if installing simulator use "./configure sim" instead) > I tried uspace and sim > debian $ ./configure uspace > unknown distribution: Gentoo-n/a > configuration may be wrong! > successfully configured for 'uspace-Gentoo-n/a'-'uspace'.. > > It never produced dpkg-checkbuilddeps I have a basic question. Why does it build this way? I mean I would think the ./configure in src would be able to detect missing dependencies. >> >> -- >> Sebastian Kuzminsky >> >> -- >> ___ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users > > > > -- > Home > http://evanfoss.googlepages.com/ > Work > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
[Emc-users] [emc-users] Building from source
Hi Folks, I am trying to build from source. I know this is not advised but I am working on debugging a gcode generator and I just want the simulator to run on my regular desktop. Compiling emc/task/emctask.cc In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, from /usr/include/boost/python/args.hpp:8, from /usr/include/boost/python.hpp:11, from emc/rs274ngc/interp_internal.hh:16, from emc/rs274ngc/rs274ngc_interp.hh:20, from emc/task/emctask.cc:29: /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory compilation terminated. Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed make: *** [objects/emc/task/emctask.o] Error 1 -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 3:20 AM, Sebastian Kuzminskywrote: > On 09/19/2015 07:00 PM, Evan Foss wrote: >> Hi Folks, >> >> I am trying to build from source. I know this is not advised but I am >> working on debugging a gcode generator and I just want the simulator >> to run on my regular desktop. >> >> >> Compiling emc/task/emctask.cc >> In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, >> from /usr/include/boost/python/args.hpp:8, >> from /usr/include/boost/python.hpp:11, >> from emc/rs274ngc/interp_internal.hh:16, >> from emc/rs274ngc/rs274ngc_interp.hh:20, >> from emc/task/emctask.cc:29: >> /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: >> pyconfig.h: No such file or directory >> compilation terminated. >> Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed >> make: *** [objects/emc/task/emctask.o] Error 1 > > Hi Evan, unfortunately our build documentation is not super easy to > find. LinuxCNC has many build dependencies. They are recorded in the > debian/configure script. Instructions on how to use it to discover what > you need to install are here: > > http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies Yes I tried that. cd debian ./configure -a (if installing simulator use "./configure sim" instead) I tried uspace and sim debian $ ./configure uspace unknown distribution: Gentoo-n/a configuration may be wrong! successfully configured for 'uspace-Gentoo-n/a'-'uspace'.. It never produced dpkg-checkbuilddeps > > -- > Sebastian Kuzminsky > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On 09/19/2015 09:42 PM, Evan Foss wrote: > On Sun, Sep 20, 2015 at 3:29 AM, Evan Fosswrote: >> On Sun, Sep 20, 2015 at 3:20 AM, Sebastian Kuzminsky >> wrote: >>> On 09/19/2015 07:00 PM, Evan Foss wrote: Hi Folks, I am trying to build from source. I know this is not advised but I am working on debugging a gcode generator and I just want the simulator to run on my regular desktop. Compiling emc/task/emctask.cc In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, from /usr/include/boost/python/args.hpp:8, from /usr/include/boost/python.hpp:11, from emc/rs274ngc/interp_internal.hh:16, from emc/rs274ngc/rs274ngc_interp.hh:20, from emc/task/emctask.cc:29: /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: pyconfig.h: No such file or directory compilation terminated. Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed make: *** [objects/emc/task/emctask.o] Error 1 >>> >>> Hi Evan, unfortunately our build documentation is not super easy to >>> find. LinuxCNC has many build dependencies. They are recorded in the >>> debian/configure script. Instructions on how to use it to discover what >>> you need to install are here: >>> >>> http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies >> >> Yes I tried that. >> cd debian >> ./configure -a (if installing simulator use "./configure sim" instead) >> I tried uspace and sim >> debian $ ./configure uspace >> unknown distribution: Gentoo-n/a >> configuration may be wrong! >> successfully configured for 'uspace-Gentoo-n/a'-'uspace'.. >> >> It never produced dpkg-checkbuilddeps > > I have a basic question. Why does it build this way? I mean I would > think the ./configure in src would be able to detect missing > dependencies. Ah, you're building on Gentoo, I didn't realize that. We do not currently have instructions for how to build on Gentoo, unfortunately. LinuxCNC currently targets/supports Debian and Debian-derived distributions like Ubuntu. There have been some efforts to develop the Gentoo build documentation, but as far as I know they have not produced any results yet. If you get your Gentoo build to work, I'd welcome an ebuild file and/or documentation. You're right that src/configure is supposed to identify missing build dependencies. If it fails at that job, that's a bug, and we'd love a patch. debian/configure and dpkg-checkbuilddeps are Debian-specific tools that do a similar but different job - they tell you, in a programmatic way, which debian packages are missing and need to be installed in order to build. -- Sebastian Kuzminsky -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 1:00 AM, Evan Fosswrote: > Hi Folks, > > I am trying to build from source. I know this is not advised but I am > working on debugging a gcode generator and I just want the simulator > to run on my regular desktop. Sorry I meant to include this. I tried this configuration ./configure --enable-simulator --without-libmodbus --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh --with-tclconfig=/usr/lib64/tclConfig.sh which fails before I can even start the build with this ... checking for --tcl support in msgfmt... yes checking for Python support... yes checking python version... OK checking version of python libraries... python2.7 checking match between tk and Tkinter versions... Traceback (most recent call last): File "", line 1, in ImportError: No module named _tkinter Traceback (most recent call last): File "", line 1, in ImportError: No module named _tkinter TCL mismatch: 8.5 vs configure: error: Python requires use of Tcl and Tk . Install this version and specify --with-tclConfig and --with-tkConfig if necessary and this one finishes the configuration but ./configure --enable-simulator --without-libmodbus --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh --with-tclconfig=/usr/lib64/tclConfig.sh --disable-python the build fails with this this > Compiling emc/task/emctask.cc > In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, > from /usr/include/boost/python/args.hpp:8, > from /usr/include/boost/python.hpp:11, > from emc/rs274ngc/interp_internal.hh:16, > from emc/rs274ngc/rs274ngc_interp.hh:20, > from emc/task/emctask.cc:29: > /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: > pyconfig.h: No such file or directory > compilation terminated. > Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed > make: *** [objects/emc/task/emctask.o] Error 1 I understand that I am minus some key dependency that autotools is not configured to catch correctly. -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
It looks like you're missing some python-related packages, namely the one that provides pyconfig.h and the one that provides _tkinter.so. On my Debian Jessie system the relevant packages seem to be libpython2.7-dev: /usr/include/python2.7/pyconfig.h python-tk: /usr/lib/python2.7/lib-dynload/_tkinter.so but different OSes and releases may have different package names. I will happily review a patch to detect this in configure and give a more useful error message. Jeff -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 4:05 AM, Kyle Kerrwrote: > Apologies for my reply. I was the stupid human posing the question. When I > read you only wanted the simulator, I thought I would ask why not just run > in a VM, but, I didn't ask in a text friendly way. It's ok. This has been a long week for me and seemingly everyone else I know/meet. No worries. > On Sat, Sep 19, 2015, 10:38 PM Jeff Epler wrote: > >> It looks like you're missing some python-related packages, namely the >> one that provides pyconfig.h and the one that provides _tkinter.so. >> >> On my Debian Jessie system the relevant packages seem to be >> libpython2.7-dev: /usr/include/python2.7/pyconfig.h >> python-tk: /usr/lib/python2.7/lib-dynload/_tkinter.so >> but different OSes and releases may have different package names. >> >> I will happily review a patch to detect this in configure and give a >> more useful error message. >> >> Jeff >> >> >> -- >> ___ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users >> > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
Stupid human question. Wouldn't running in a VM be quicker, easier, and less painful? On Sat, Sep 19, 2015, 9:08 PM Evan Fosswrote: > On Sun, Sep 20, 2015 at 1:00 AM, Evan Foss wrote: > > Hi Folks, > > > > I am trying to build from source. I know this is not advised but I am > > working on debugging a gcode generator and I just want the simulator > > to run on my regular desktop. > > Sorry I meant to include this. I tried this configuration > > ./configure --enable-simulator --without-libmodbus > --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh > --with-tclconfig=/usr/lib64/tclConfig.sh > > which fails before I can even start the build with this > ... > checking for --tcl support in msgfmt... yes > checking for Python support... yes > checking python version... OK > checking version of python libraries... python2.7 > checking match between tk and Tkinter versions... Traceback (most > recent call last): > File "", line 1, in > ImportError: No module named _tkinter > Traceback (most recent call last): > File "", line 1, in > ImportError: No module named _tkinter > TCL mismatch: 8.5 vs > configure: error: Python requires use of Tcl and Tk . > Install this version and specify --with-tclConfig and --with-tkConfig > if necessary > > and this one finishes the configuration but > > ./configure --enable-simulator --without-libmodbus > --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh > --with-tclconfig=/usr/lib64/tclConfig.sh --disable-python > > the build fails with this this > > > Compiling emc/task/emctask.cc > > In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, > > from /usr/include/boost/python/args.hpp:8, > > from /usr/include/boost/python.hpp:11, > > from emc/rs274ngc/interp_internal.hh:16, > > from emc/rs274ngc/rs274ngc_interp.hh:20, > > from emc/task/emctask.cc:29: > > /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: > > pyconfig.h: No such file or directory > > compilation terminated. > > Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed > > make: *** [objects/emc/task/emctask.o] Error 1 > > I understand that I am minus some key dependency that autotools is not > configured to catch correctly. > > -- > Home > http://evanfoss.googlepages.com/ > Work > http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ > > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users > -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 2:15 AM, Kyle Kerrwrote: > Stupid human question. Wouldn't running in a VM be quicker, easier, and > less painful? I don't want the over head from that. This is a documented feature of your code so not being able to build it is a bug. I did my due diligence and searched for similar reports before I sent my bug report. I found one other case of this being reported but no solution, just another person from your group saying "can't you just not use this". I understand that building the real time stuff to support an actual full install is not something you want to undertake but the simulator should build on a sane user space environment. > On Sat, Sep 19, 2015, 9:08 PM Evan Foss wrote: > >> On Sun, Sep 20, 2015 at 1:00 AM, Evan Foss wrote: >> > Hi Folks, >> > >> > I am trying to build from source. I know this is not advised but I am >> > working on debugging a gcode generator and I just want the simulator >> > to run on my regular desktop. >> >> Sorry I meant to include this. I tried this configuration >> >> ./configure --enable-simulator --without-libmodbus >> --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh >> --with-tclconfig=/usr/lib64/tclConfig.sh >> >> which fails before I can even start the build with this >> ... >> checking for --tcl support in msgfmt... yes >> checking for Python support... yes >> checking python version... OK >> checking version of python libraries... python2.7 >> checking match between tk and Tkinter versions... Traceback (most >> recent call last): >> File "", line 1, in >> ImportError: No module named _tkinter >> Traceback (most recent call last): >> File "", line 1, in >> ImportError: No module named _tkinter >> TCL mismatch: 8.5 vs >> configure: error: Python requires use of Tcl and Tk . >> Install this version and specify --with-tclConfig and --with-tkConfig >> if necessary >> >> and this one finishes the configuration but >> >> ./configure --enable-simulator --without-libmodbus >> --enable-run-in-place --with-tkConfig=/usr/lib64/tkConfig.sh >> --with-tclconfig=/usr/lib64/tclConfig.sh --disable-python >> >> the build fails with this this >> >> > Compiling emc/task/emctask.cc >> > In file included from /usr/include/boost/python/detail/prefix.hpp:13:0, >> > from /usr/include/boost/python/args.hpp:8, >> > from /usr/include/boost/python.hpp:11, >> > from emc/rs274ngc/interp_internal.hh:16, >> > from emc/rs274ngc/rs274ngc_interp.hh:20, >> > from emc/task/emctask.cc:29: >> > /usr/include/boost/python/detail/wrap_python.hpp:50:23: fatal error: >> > pyconfig.h: No such file or directory >> > compilation terminated. >> > Makefile:215: recipe for target 'objects/emc/task/emctask.o' failed >> > make: *** [objects/emc/task/emctask.o] Error 1 >> >> I understand that I am minus some key dependency that autotools is not >> configured to catch correctly. >> >> -- >> Home >> http://evanfoss.googlepages.com/ >> Work >> http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ >> >> >> -- >> ___ >> Emc-users mailing list >> Emc-users@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/emc-users >> > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
Re: [Emc-users] [emc-users] Building from source
On Sun, Sep 20, 2015 at 3:58 AM, Sebastian Kuzminskywrote: > On 09/19/2015 09:42 PM, Evan Foss wrote: >> On Sun, Sep 20, 2015 at 3:29 AM, Evan Foss wrote: >>> On Sun, Sep 20, 2015 at 3:20 AM, Sebastian Kuzminsky >>> wrote: On 09/19/2015 07:00 PM, Evan Foss wrote: Hi Evan, unfortunately our build documentation is not super easy to find. LinuxCNC has many build dependencies. They are recorded in the debian/configure script. Instructions on how to use it to discover what you need to install are here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies >>> >>> Yes I tried that. >>> cd debian >>> ./configure -a (if installing simulator use "./configure sim" instead) >>> I tried uspace and sim >>> debian $ ./configure uspace >>> unknown distribution: Gentoo-n/a >>> configuration may be wrong! >>> successfully configured for 'uspace-Gentoo-n/a'-'uspace'.. >>> >>> It never produced dpkg-checkbuilddeps >> >> I have a basic question. Why does it build this way? I mean I would >> think the ./configure in src would be able to detect missing >> dependencies. > > Ah, you're building on Gentoo, I didn't realize that. We do not Sorry I omitted that. This machine has an i7 running in 64 bit. cat /proc/version Linux version 3.19.1 (root@turingatlarge) (gcc version 4.7.3 (Gentoo 4.7.3-r1 p1.4, pie-0.5.5) ) #1 SMP Sun Mar 15 14:26:53 EST 2015 I was hoping this was a minor issue that was just previously unreported so I got a little lazy. > currently have instructions for how to build on Gentoo, unfortunately. > LinuxCNC currently targets/supports Debian and Debian-derived > distributions like Ubuntu. There have been some efforts to develop the > Gentoo build documentation, but as far as I know they have not produced > any results yet. If you get your Gentoo build to work, I'd welcome an > ebuild file and/or documentation. I am trying to fix issues in gEDA PCB. The project has been stalled for some time so they have piled up. Normally I would write a patch for your but right now I have my own unhappy user to contend with. I will however do everything I can to break down where this is going wrong and document it. An ebuild would be nice but so many things are required for real time to work so any ebuild would really have to be for simulation only. Doing that would lead to a flood of users requesting expansion to full functionality. > You're right that src/configure is supposed to identify missing build > dependencies. If it fails at that job, that's a bug, and we'd love a patch. > > debian/configure and dpkg-checkbuilddeps are Debian-specific tools that > do a similar but different job - they tell you, in a programmatic way, > which debian packages are missing and need to be installed in order to > build. > > > -- > Sebastian Kuzminsky > > -- > ___ > Emc-users mailing list > Emc-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-users -- Home http://evanfoss.googlepages.com/ Work http://forge.abcd.harvard.edu/gf/project/epl_engineering/wiki/ -- ___ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users