Back
[07:57:05] <KGB-linuxcnc> 03John Thornton 05master dd36a70 06linuxcnc 10docs/src/gcode/overview.txt Docs: fix duplicate element anchor * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=dd36a70
[11:28:37] <KGB-linuxcnc> 03John Thornton 05master eab3c4b 06linuxcnc 10docs/src/config/copy_and_run_es.txt 10docs/src/config/stepconf_es.txt Docs: fix broken links in Spanish Docs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=eab3c4b
[11:40:39] <andypugh> Well, I never expected to have to edit keystick.cc !
[13:27:15] <jthornton> seb_kuzminsky, down to one error tbl:fatal error: can't open `man1/linuxcnc.1': No such file or directory
[14:01:11] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 2119397 06linuxcnc 10docs/src/Submakefile 10src/Makefile docs: make linuxcnc.1 in the docs: target * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=2119397
[14:01:49] <seb_kuzminsky> jthornton: down to 0
[14:01:51] <seb_kuzminsky> i hope ;-)
[14:38:15] <seb_kuzminsky> i'd like to put the linux 3.4.55 rtai kernel in the debian archive at www.linuxcnc.org
[14:38:32] <seb_kuzminsky> it's not without wrinkles, but it would benefit from wider testing
[14:38:43] <seb_kuzminsky> i've been running my bridgeport with it and haven't had any problems at all
[14:39:14] <seb_kuzminsky> putting it in a publically visible deb archive would let the buildbot build precise-rtai debs
[14:39:37] <seb_kuzminsky> i'll try to support the new rtai kernel if people start testing it
[14:39:40] <seb_kuzminsky> any objections?
[15:06:07] <andypugh> None from me
[15:08:55] <seb_kuzminsky> docs in master now builds without any warnings :-)
[15:08:59] <seb_kuzminsky> thanks jthornton
[15:09:10] <seb_kuzminsky> http://buildbot.linuxcnc.org/buildbot/builders/docs/builds/1164
[15:37:58] <enis__> hello
[15:40:21] <enis__> can you help me about linuxcnc on beaglebone?
[15:44:32] <andypugh> Ask your question, it might be something that someone here knows the answer to.
[15:45:08] <andypugh> You might have a larger audience on #linuxcnc
[15:45:12] <enis__> I actually want to know which pins are used by linuxcnc as step-dir signals
[15:45:30] <andypugh> Are you using the PRU code?
[15:46:23] <andypugh> Or are you using software step generation?
[15:47:07] <enis__> I will use machinekit image
[15:48:25] <andypugh> Caped or Capeless?
[15:48:36] <enis__> capeless
[15:49:35] <andypugh> This might help:
http://thread.gmane.org/gmane.linux.distributions.emc.user/47846/focus=47915
[15:53:47] <enis__> thanks
[15:57:54] <andypugh> Is there a way to not be told off for using " if (PyMapping_HasKeyString(ret.ptr(), "Error")) " ? (deprecated conversion of const string to char* )
[16:00:33] <seb_kuzminsky> linuxcnc-build: force build --branch=master checkin
[16:00:34] <linuxcnc-build> build #1505 forced
[16:00:34] <linuxcnc-build> I'll give a shout when the build finishes
[16:50:00] <linuxcnc-build> build #0 of package-rt-precise-source is complete: Failure [4failed shell] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/package-rt-precise-source/builds/0
[17:06:27] <linuxcnc-build> build #1505 of checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/checkin/builds/1505
[17:56:41] <seb_kuzminsky> linuxcnc-build: force build --branch=v2.5_branch checkin
[17:56:42] <linuxcnc-build> build #1506 forced
[17:56:42] <linuxcnc-build> I'll give a shout when the build finishes
[17:56:56] <seb_kuzminsky> we'll see how the 2.5 docs do...
[18:59:05] <jepler> andypugh: only method i k
[19:00:18] <jepler> andypugh: only method I know of is explicit const_cast<char*>
[19:01:19] <andypugh> Isn't the problem the reverse? The function input is a char* but the "Error" string is a const literal?
[19:03:01] <andypugh> Anyway, my decision is to ignore it and push the branch. I think I am likely to start again from the beginning
[19:15:49] <andypugh> http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=blob;f=src/emc/nml_intf/emc_nml.hh;h=c2212e9eeb2a1988811c5abc3dcbfa719caaf58a;hb=HEAD#l1562 is a C++ class that exposes an array. Would it be possible for that class to have an actual OO Method, that uses Boost::Python to call Python code to access an SQL database (or, potentially, to acces the SQL itself?). Given that it is passed along as an NML message, and could be
[19:15:50] <andypugh> anywhere, how likely is it that Methods would be in the wrong namespace or memory space, or even on the wrong hardware, to actually work?
[19:15:58] <linuxcnc-build> build #1166 of docs is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/docs/builds/1166
[19:16:00] <linuxcnc-build> build #1506 of checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/checkin/builds/1506
[19:40:42] <KGB-linuxcnc> 03andypugh 05tooltable f41f441 06linuxcnc 10(11 files in 2 dirs) Tool database as a database * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=f41f441
[19:40:42] <KGB-linuxcnc> 03Andy Pugh 05tooltable 9fd6617 06linuxcnc 10(20 files in 5 dirs) starting to play with interp-convert * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=9fd6617
[19:40:43] <KGB-linuxcnc> 03andypugh 05tooltable 4197c5f 06linuxcnc 10(10 files in 6 dirs) First working version * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=4197c5f
[19:40:44] <KGB-linuxcnc> 03andypugh 05tooltable 870b00b 06linuxcnc 03lib/python/toolstore/test.py 03lib/python/toolstore/tool_db 03share/sql/classic.sql Add some missed files * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=870b00b
[19:40:48] <KGB-linuxcnc> 03Andy Pugh 05tooltable bfe0a76 06linuxcnc 10(6 files in 5 dirs) Teach Axis and ioControl how to work the database * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=bfe0a76
[19:40:52] <KGB-linuxcnc> 03Andy Pugh 05tooltable 96fcc95 06linuxcnc 10(809 files in 105 dirs) This commit must never be merged!! Comments and sample config for the tool-database branch * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=96fcc95
[20:28:00] <jepler> andypugh: yes, and Python doesn't correctly note that it's OK to pass a const char* to that argument
[20:46:01] <linuxcnc-build> build #1504 of precise-i386-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-i386-sim/builds/1504 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:47:12] <linuxcnc-build> build #707 of precise-i386-realtime-rip is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-i386-realtime-rip/builds/707 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:47:44] <linuxcnc-build> build #1506 of precise-amd64-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-amd64-sim/builds/1506 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:50:58] <linuxcnc-build> build #1503 of lucid-i386-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-i386-sim/builds/1503 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:53:49] <linuxcnc-build> build #1507 of hardy-amd64-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-amd64-sim/builds/1507 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:58:32] <linuxcnc-build> build #1505 of hardy-i386-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-i386-sim/builds/1505 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:59:18] <linuxcnc-build> build #1505 of lucid-amd64-sim is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-amd64-sim/builds/1505 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[20:59:20] <linuxcnc-build> build #1502 of hardy-i386-realtime-rip is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-i386-realtime-rip/builds/1502 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[21:02:37] <linuxcnc-build> build #1506 of lucid-i386-realtime-rip is complete: Failure [4failed compile runtests] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-i386-realtime-rip/builds/1506 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[21:02:38] <linuxcnc-build> build #1507 of checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/checkin/builds/1507 blamelist: andypugh <andy@bodgesoc.org>, Andy Pugh <andy@bodgesoc.org>
[21:05:33] <linuxcnc-build> build #708 of precise-i386-realtime-rip is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-i386-realtime-rip/builds/708 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:07:49] <linuxcnc-build> build #1505 of precise-i386-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-i386-sim/builds/1505 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:08:56] <linuxcnc-build> build #1507 of precise-amd64-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-amd64-sim/builds/1507 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:09:55] <linuxcnc-build> build #1507 of lucid-i386-realtime-rip is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-i386-realtime-rip/builds/1507 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:09:57] <linuxcnc-build> build #1302 of precise-amd64-sim-clang is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/precise-amd64-sim-clang/builds/1302 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:10:08] <linuxcnc-build> build #1504 of lucid-i386-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-i386-sim/builds/1504 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:11:17] <linuxcnc-build> build #1503 of lucid-rtai-i386-clang is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-rtai-i386-clang/builds/1503 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:11:57] <linuxcnc-build> build #1506 of lucid-amd64-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/lucid-amd64-sim/builds/1506 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:12:45] <linuxcnc-build> build #1508 of hardy-amd64-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-amd64-sim/builds/1508 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:12:54] <linuxcnc-build> build #1503 of hardy-i386-realtime-rip is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-i386-realtime-rip/builds/1503 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:13:01] <linuxcnc-build> build #1506 of hardy-i386-sim is complete: Failure [4failed compile] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/hardy-i386-sim/builds/1506 blamelist: Andy Pugh <andy@bodgesoc.org>
[21:13:01] <linuxcnc-build> build #1508 of checkin is complete: Failure [4failed] Build details are at
http://buildbot.linuxcnc.org/buildbot/builders/checkin/builds/1508 blamelist: Andy Pugh <andy@bodgesoc.org>
[22:47:31] <KGB-linuxcnc> 03Sebastian Kuzminsky 05master 519bb5d 06linuxcnc 10debian/rules.in deb: provide build-arch and build-indep targets in debian/rules * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=519bb5d
[23:02:59] <seb_kuzminsky> are there instructions anywhere on how to work with the debian archive at w.l.o/dists? someone wanna walk me through it and i'll take notes & write it up