#linuxcnc-devel | Logs for 2014-11-30

[00:01:38] <Tom_itx> so do i want branch 2.7 or master?
[00:04:51] <pcw_home> For a real machine?
[00:05:43] <Tom_itx> yes
[00:05:49] <Tom_itx> well for testing
[00:06:42] <pcw_home> Unless theres something you need from master, I think 2.7 would be preferred (closer to release)
[00:10:35] <Tom_itx> yeah i went for master
[00:10:44] <Tom_itx> i can recompile it later
[00:12:28] <Tom_itx> i gotta wait until i get my boards fixed / replaced anyway
[12:55:47] <skunkworks> zlog:
[14:22:02] <Tom_itx> skunkworks have you been testing 2.7 or master?
[14:22:35] <Tom_itx> any major differences?
[14:36:08] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.7 a4d594b 06linuxcnc 10docs/src/gui/axis_fr.txt 04docs/src/gui/images/axis_25_fr.png docs: deduplicate an image in the french docs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a4d594b
[14:36:21] <seb_kuzm1nsky> Tom_itx: 2.7 and master are pretty close still
[14:36:53] <seb_kuzminsky> if you're going to test new versions of linuxcnc, i'd suggest 2.7 since that's what we're trying to stabilize for release
[14:43:05] <Tom_itx> i gotta get some hardware back together before i can test anything
[14:44:16] <Tom_itx> what's this moveoff thing? is that for things like changing cutters and resuming?
[14:46:51] <seb_kuzminsky> Tom_itx: yeap
[14:47:00] <seb_kuzminsky> it's kind of a poor man's jog-while-paused
[14:47:16] <Tom_itx> it would be a very handy feature
[14:47:22] <seb_kuzminsky> heh
[14:47:40] <seb_kuzminsky> yeah, our users sure are enthusiastic about somebody adding it
[14:47:52] <Tom_itx> i mentioned it a couple years ago
[14:48:18] <seb_kuzminsky> it's been talked about a lot, for a long time
[14:48:21] <Tom_itx> the only way now is to rerun the whole tool path or run from line but you need to be in position for that
[14:51:27] <Tom_itx> probably not the easiest thing to code...
[14:52:10] <seb_kuzminsky> yeah
[14:52:47] <Tom_itx> especially with the new TP lookahead
[14:53:19] <Tom_itx> does it keep track of what line it's executed?
[14:53:22] <seb_kuzminsky> it's conceptually fairly straight-forward, but doing it the "conceptually simple" way requires changing a part of linuxcnc called Task, which is old and crufty and easy to break and difficult to fix
[14:54:36] <seb_kuzminsky> there's an effort underway called "lui" or "liblinuxcnc-ui" that will eventually lead to a cleanup of Task, which will make things like jwp easier/safer to implement
[14:55:07] <seb_kuzminsky> dgarr's moveoff is a wonderful clean way to get like 80% of jwp without any risk
[14:56:14] <Tom_itx> i hope all these patches don't interfere with the big picture
[14:56:20] <seb_kuzminsky> except the risk of angry users, of course
[14:56:51] <Tom_itx> seems to be fairly user driven anyway
[14:57:01] <seb_kuzminsky> there have been a couple of jwp patches floating around that made things worse in the big-picture sense, which is why we haven't merged it
[14:57:29] <seb_kuzminsky> dgarr's patch is just a new hal component, so it doesn't affect Task or the big picture
[14:57:43] <seb_kuzminsky> which is why it's a very likely merge candidate for 2.7
[14:57:55] <Tom_itx> it's not in 2.7 yet then?
[14:58:16] <seb_kuzminsky> right, he's (correctly) developing it in a feature branch called dgarr/moveoff
[14:58:30] <seb_kuzminsky> if you're in a testing mood, that'd be a great one to provide feedback on
[14:58:43] <seb_kuzminsky> especially if you care about jwp
[14:58:49] <Tom_itx> once i get my mesa cards figured out i may do that
[14:58:56] <seb_kuzminsky> cool
[14:59:03] <Tom_itx> i blew out all the 5v on them for some unknown reason
[14:59:09] <seb_kuzminsky> ouch
[14:59:18] <Tom_itx> need to figure out why before adding more
[15:00:34] <Tom_itx> and i get limited play time so it could be a while
[15:00:52] <seb_kuzminsky> yeah, i can relate to that...
[15:01:02] <seb_kuzminsky> so many projects, so little time
[15:01:57] <Tom_itx> i wish i could code better and knew the innards of lcnc... i enjoy doing that sort of thing
[15:02:34] <Tom_itx> unfortunately i didn't grow up with linux
[15:06:36] <Tom_itx> i'll rebuild master for 2.7 then
[15:17:57] <seb_kuzminsky> hrm, force-pushing a branch after a rebase that involves many commits takes forever
[15:28:33] <seb_kuzminsky> neat! http://www.phoronix.com/scan.php?page=news_item&px=MTg1MTM
[15:28:38] <seb_kuzminsky> i wonder what the latency is like
[15:28:52] <KGB-linuxcnc> 03Sebastian Kuzminsky 05scorbot-er-3 34652b6 06linuxcnc 10debian/control.in 10src/Makefile 10src/hal/user_comps/Submakefile 03src/hal/user_comps/scorbot-er-3.py add a non-realtime driver for the scorbot-er-3 robot arm * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=34652b6
[15:28:52] <KGB-linuxcnc> 03Sebastian Kuzminsky 05scorbot-er-3 e8cc2b8 06linuxcnc 03configs/by_machine/scorbot-er-3/pyvcp.hal 03configs/by_machine/scorbot-er-3/pyvcp.xml 03configs/by_machine/scorbot-er-3/scorbot-er-3.hal 03configs/by_machine/scorbot-er-3/scorbot-er-3.ini add a sample config for the scorbot-er-3 robot arm * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=e8cc2b8
[15:29:41] <seb_kuzminsky> wow, that push took like 15 minutes
[15:30:20] <Tom_itx> not a bad lookin board
[15:45:53] <seb_kuzminsky> yeah, and coreboot is exciting to me
[15:47:09] <Tom_itx> well that built the wrong branch
[15:47:52] <seb_kuzminsky> are you trying to build 2.7 but getting master in stead?
[15:48:06] <Tom_itx> no i built master and was trying to build 2.7
[15:48:11] <Tom_itx> and got 2.5.4
[15:48:26] <Tom_itx> did a git branch 2.7
[15:49:32] <Tom_itx> i'm not that git savvy either...
[15:50:37] <pcw_home> you want to:
[15:50:39] <pcw_home> git checkout 2.7
[15:50:45] <memfrob> git checkout.. beat me to it
[15:50:57] <atom1> i did that after git branch 2.7
[15:51:00] <atom1> then git checkout
[15:51:53] <atom1> does it matter if i 'make clean' first?
[15:53:01] <atom1> ok i think i figured it out
[15:53:09] <pcw_home> what I do is this
[15:53:10] <pcw_home> git checkout 2.7
[15:53:12] <pcw_home> git pull
[15:53:13] <pcw_home> git branch (to check which branch is checked out if paranoid)
[15:53:19] <atom1> yeah
[15:54:17] <seb_kuzminsky> i do this:
[15:54:20] <seb_kuzminsky> git fetch origin
[15:54:28] <seb_kuzminsky> git checkout 2.7
[15:54:34] <seb_kuzminsky> git merge --ff-only origin/2.7
[15:55:08] <seb_kuzminsky> (that's assuming i already have a local branch called 2.7, which points at some earlier commit in origin/2.7 from glo)
[15:55:44] <atom1> it shows 2.7 in the list when i 'git branch -r'
[15:56:58] <pcw_home> it should show every possible branch at glo, many of which are experimental or dead-ends
[15:57:30] <atom1> Not possible to fast-forward, aborting.
[15:58:55] <KGB-linuxcnc> 03Chris Morley 05pnc-spindle-work ffa2cfe 06linuxcnc 10src/emc/usr_intf/pncconf/external.glade 10src/emc/usr_intf/pncconf/pages.py pncconf -wip for external page * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ffa2cfe
[15:58:55] <KGB-linuxcnc> 03chris morley 05pnc-spindle-work ed38be2 06linuxcnc 10src/emc/usr_intf/pncconf/build_HAL.py pncconf -fix HAL file built with new spindle work * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=ed38be2
[15:58:55] <KGB-linuxcnc> 03chris morley 05pnc-spindle-work 6bf6b1b 06linuxcnc 10src/emc/usr_intf/pncconf/pncconf.py pncconf -fix passing of values from scale dialogs * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=6bf6b1b
[15:58:57] <KGB-linuxcnc> 03chris morley 05pnc-spindle-work 47cb91c 06linuxcnc 10src/emc/usr_intf/pncconf/tests.py pncconf -don't assume an encoder on spindle tests * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=47cb91c
[15:59:01] <KGB-linuxcnc> 03chris morley 05pnc-spindle-work d986b7f 06linuxcnc 10src/emc/usr_intf/pncconf/s_motor.glade pncconf -hide the test/tune button on the spindle page * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=d986b7f
[15:59:15] <seb_kuzminsky> if you can't fast-forward, then you're not in the right place, or you have local commits that need to be rebased or merged
[15:59:45] <atom1> no commits
[15:59:51] <atom1> it says i'm on 2.7 though
[15:59:56] <atom1> compiling...
[15:59:58] <seb_kuzminsky> if you haven't made local commits to your 2.7 branch, then it got set to point to the wrong place
[16:00:56] <seb_kuzminsky> what's the first line of "git show 2.7" say?
[16:01:09] <atom1> i'll let you know when it's done
[16:01:48] <atom1> commit 0c55c195942782b8dcf22caa5ff8f49591880c6d
[16:02:09] <seb_kuzminsky> ok great!
[16:02:22] <seb_kuzminsky> what does "git branch --contains (that sha)" say?
[16:02:41] <seb_kuzminsky> that'll list all the branches that have that commit in their history
[16:03:05] <atom1> 2.7 & master
[16:03:24] <seb_kuzminsky> aha
[16:03:38] <atom1> i built master first
[16:03:47] <seb_kuzminsky> and "git branch -r --contains (the sha)"?
[16:03:51] <atom1> then thought i switched to 2.7
[16:04:01] <seb_kuzminsky> i should've said that first
[16:04:08] <seb_kuzminsky> the -r means "include remote branches
[16:04:47] <atom1> tom@atom1:~/linuxcnc-master$ git branch -r --contains
[16:04:47] <atom1> origin/HEAD -> origin/master
[16:04:47] <atom1> origin/dgarr/moveoff
[16:04:47] <atom1> origin/master
[16:04:47] <atom1> origin/pnc-spindle-work
[16:05:05] <seb_kuzminsky> TIL atom1 == Tom
[16:05:14] <atom1> yep
[16:06:03] <seb_kuzminsky> and that list must include your local 2.7, like you said before, but not origin/2.7
[16:06:30] <seb_kuzminsky> which means your local 2.7 branch points at a commit that's not in origin/2.7, so something got messed up when you created it
[16:06:41] <seb_kuzminsky> were you on the master branch, then said "git branch 2.7"?
[16:06:47] <atom1> i'll just get it again
[16:07:01] <atom1> i think that's what i did
[16:07:08] <seb_kuzminsky> ok, that's the problem
[16:07:29] <seb_kuzminsky> "git branch $NEW_NAME" means "create a new branch named $NEW_NAME, pointing at the commit i'm currently on"
[16:07:47] <atom1> woops
[16:08:13] <seb_kuzminsky> you maybe meant "git branch 2.7 origin/2.7", which means create a new branch called 2.7, pointing at the commit that origin/2.7 points to
[16:08:28] <seb_kuzminsky> at this point, if you're on 2.7, you can fix it by saying "git reset --hard origin/2.7"
[16:08:59] <seb_kuzminsky> that means "throw away my working directory, make my current branch point to the commit that origin/2.7 points to, and check that out"
[16:09:13] <atom1> HEAD is now at a4d594b docs: deduplicate an image in the french docs
[16:09:27] <seb_kuzminsky> great, that's the commit i just pushed to 2.7 earlier today
[16:09:43] <atom1> so we're ready to compile now?
[16:10:30] <seb_kuzminsky> yep
[16:11:44] <atom1> so confusing...
[16:12:07] <seb_kuzminsky> yeah, git can be real confusing
[16:12:25] <atom1> so if i'm on master and want to switch to another branch what do i do?
[16:12:53] <atom1> i thought git branch <name> did it...
[16:12:59] <seb_kuzminsky> the trick for me to understanding git was to learn about the underlying data structures it uses, and how the common commands manipulate those structures
[16:13:11] <jepler> what is scorbot-er-3 ?
[16:13:40] <jepler> ah I see
[16:13:48] <seb_kuzminsky> atom1: from our "Contributing to LinuxCNC" document: http://git-scm.com/book/en/v2
[16:14:19] <seb_kuzminsky> atom1: if i'm on a branch and want to switch to another branch, i do this
[16:14:27] <jepler> seb_kuzminsky: so you get non-realtime control of position with that setup?
[16:14:32] <seb_kuzminsky> git checkout $NEW_BRANCH
[16:14:55] <seb_kuzminsky> the "checkout" (instead of "branch") is important
[16:15:00] <seb_kuzminsky> jepler: yep
[16:15:01] <atom1> ok
[16:15:18] <atom1> i think i see what i did
[16:16:15] <seb_kuzminsky> jepler: it's pretty awful and jerky, but it was quick to do and it is usable by existing scorbot er-3 owners
[16:17:13] <seb_kuzminsky> "quick"
[16:21:41] <jepler> hmmm
[16:21:52] <jepler> I wonder if it's feasible to put a test of genhexkins and/or genserkins in tests/
[16:22:03] <jepler> go to world position + read out joint position
[16:22:10] <jepler> tuits
[16:22:14] <jepler> -ENOTUITS
[16:27:36] <seb_kuzminsky> that seems feasible
[16:31:03] <atom1> still ended up with 2.5.4 :(
[16:32:07] <seb_kuzminsky> atom1: that does *not* seem feasible
[16:32:29] <atom1> unless the signon hasn't been changed
[16:32:43] <atom1> tom@atom1:~/linuxcnc-master$ linuxcnc
[16:32:43] <atom1> LINUXCNC - 2.5.4
[16:33:14] <seb_kuzminsky> atom1: 'which linuxcnc'?
[16:33:21] <seb_kuzminsky> it may be you have 2.5.4 installed via the deb
[16:33:28] <atom1> i bet that's it
[16:33:31] <seb_kuzminsky> and forgot to run 'scripts/rip-environment'
[16:33:47] <seb_kuzminsky> well, good luck! bbl
[16:33:51] <atom1> git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-master
[16:33:55] <atom1> what what i did
[16:35:40] <micges> atom1: that's correcyt
[16:36:04] <atom1> i'm gonna start over clean
[16:36:07] <micges> then git checkout 2.7
[16:36:07] <seb_kuzminsky> that'll work, but it's misleading to name the repo 'linuxcnc-master', since you can check any branch out in it
[16:36:21] <atom1> probably so
[16:36:23] <seb_kuzminsky> the preferred name for the local repo is 'linuxcnc-dev'
[16:38:11] <atom1> i don't need git checkout origin/2.7 ? just 2.7 ?
[16:38:39] <atom1> i think i see where i went wrong the first time
[16:38:56] <atom1> i made a branch under master called 2.7 instead of checkout 2.7
[16:40:05] <micges> just 2.7
[16:40:32] <Tom_itx> ok
[17:49:55] <atom1> i don't get it. i still end up with 2.5.4
[17:50:43] <atom1> here's what i did:
[17:50:45] <atom1> git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev
[17:51:18] <skunkworks> that should give you master - 2.8pre..
[17:51:30] <atom1> cd linuxcnc-dev/src
[17:51:34] <atom1> git checkout 2.7
[17:52:08] <atom1> ./autogen.sh
[17:52:11] <atom1> ./configure
[17:52:14] <atom1> make clean
[17:52:15] <atom1> make
[17:52:21] <atom1> sudo make setuid
[17:52:42] <atom1> . ./scripts/rip-environment
[17:52:45] <atom1> linuxcnc
[17:52:53] <atom1> and it returns 2.5.4
[17:54:11] <atom1> skunkworks, and it did the first time i compiled it as master
[17:55:47] <skunkworks> I am not an expert of git foo - did you reuse a directory that you all ready had built linuxcnc?
[17:56:22] <atom1> no
[17:56:29] <atom1> i created a new one this time
[17:56:32] <atom1> tom@atom1:~/linuxcnc-dev$ git merge --ff-only origin/2.7
[17:56:32] <atom1> Already up-to-date.
[17:56:51] <atom1> that all indicates i'm on the right branch
[17:56:57] <atom1> far as i can tell
[17:57:19] <micges> what git reuturned after 'git checkout 2.7' ?
[17:57:49] <atom1> tom@atom1:~/linuxcnc-dev$ git checkout 2.7
[17:57:49] <atom1> Already on '2.7'
[17:57:58] <skunkworks> skunkworks@skunkworks-Studio-XPS-1645:~/linuxcnc-2.8$ linuxcncLINUXCNC - 2.8.0~pre1
[17:58:25] <atom1> i just started over fresh
[17:58:56] <micges> atom1: not now, the first time you entered it afterclone
[17:58:59] <atom1> i'm not on wheezy though i'm on ubuntu 10.04
[17:59:24] <atom1> pretty sure it was the same
[17:59:38] <skunkworks> this machine is 14.04
[18:01:05] <atom1> i'll go thru it one more time...
[18:02:01] <micges> hold on
[18:02:06] <atom1> too late
[18:02:18] <micges> ok clone it and wait
[18:03:27] <atom1> git clone git://git.linuxcnc.org/git/linuxcnc.git linuxcnc-dev
[18:03:30] <atom1> first step.
[18:04:32] <micges> hold on finishing clone here..
[18:04:47] <atom1> it'll take a bit here
[18:04:55] <atom1> 23%
[18:04:58] <micges> here to
[18:05:00] <micges> 70%
[18:07:41] <KimK> Hi gents. Sorry, I just got here, but back 20-30 lines I saw "cd linuxcnc-dev/src" , is that correct? I've been doing checkout (and other git stuff) from linuxcnc-dev, have I been doing it wrong?
[18:09:54] <micges> KimK: does it works for you?
[18:10:25] <micges> atom1: ok cloned
[18:10:55] <atom1> 84%
[18:11:12] <atom1> next step?
[18:11:19] <atom1> cloned here as well
[18:11:29] <KimK> I'm glad to find a small crowd here, I wanted to ask for advice. What OS is in fashion lately for linuxcnc. I see talk of Debian Wheezy. Anyone still using Ubuntu (14.04 now?). Has anyone tried to put linuxcnc on Mint?
[18:11:57] <atom1> i'm working on putting it on 10.04 ubuntu
[18:11:59] <micges> atom1: http://pastebin.com/qv0TUkLv
[18:12:50] <micges> atom1: br = branch, co = checkout
[18:13:02] <KimK> micges: Yes, I recall it working for me that way in the past, but I haven't been doing a lot with git lately.
[18:13:21] <KimK> At least not until just lately.
[18:13:42] <atom1> tom@atom1:~/linuxcnc-dev$ git branch
[18:13:43] <atom1> * master
[18:14:22] <atom1> tom@atom1:~/linuxcnc-dev$ git checkout 2.7
[18:14:22] <atom1> Branch 2.7 set up to track remote branch 2.7 from origin.
[18:14:22] <atom1> Switched to a new branch '2.7'
[18:14:45] <micges> yes that's good
[18:14:55] <atom1> as it did the last time
[18:15:19] <micges> atom1: 'cat VERSION' ?
[18:15:37] <atom1> 2.7.0~pre2
[18:15:40] <KimK> atom1: You're doing it from scratch to build 2.7 on 10.04?
[18:15:47] <atom1> yes
[18:16:12] <micges> atom1: you're on 2.7
[18:16:27] <atom1> ok i'll build it
[18:16:32] <pcw_home> KimK: I've always done the git operations from the top level (maybe wrong but seems OK)
[18:16:33] <pcw_home> (and I am running Ubuntu 14.04 with linuxcnc here)
[18:17:07] <atom1> i still do the ./autogen.sh from src right?
[18:17:13] <micges> yes
[18:17:18] <atom1> then ./configure
[18:17:49] <micges> atom1: how did you start linuxcnc after build?
[18:18:12] <atom1> sudo make setuid
[18:18:26] <atom1> . ./scripts/rip-environment
[18:18:29] <atom1> linuxcnc
[18:19:12] <micges> try go to scripts dir and type ./linuxcnc
[18:19:28] <atom1> i will when it's doen
[18:19:30] <atom1> done*
[18:20:01] <pcw_home> did you go back to ~/linuxcnc-dev before . ./scripts/rip-environment?
[18:20:08] <atom1> yes
[18:20:40] <pcw_home> and ran linuxcnc from the same shell?
[18:20:47] <atom1> it built master just fine the first time i did it
[18:20:49] <atom1> yes
[18:21:47] <KimK> pcw_home: Hi Peter. Yes, 10.04 is still my main system here too, but after a long delay I'm again looking around for an OS and a new LinuxCNC for my other PCs, Unit1 and Unit2 ("Thing 1" and "Thing 2"?).
[18:22:07] <pcw_home> strange, I dont think I have ever seen that behaviour , though I dont build on 10.04 very often
[18:26:55] <KimK> My search has become more urgent now because a recent update has hosed something in 12.04 and it no longer recognizes eth0, my internet connection. Boot to 10.04 and eth0 is fine, but 10.04 is a little clunky on the CPU/GPU, it can't do 1920x1080, has to settle for 1280x1024 or something, looks stretched/compressed.
[18:27:20] <atom1> i had that happen to me on 10.04 once
[18:28:14] <atom1> couldn't figure it out so reinstalled from the iso
[18:31:34] <KimK> Glad that fixed it for you, it didn't for me. I fiddled and fiddled, played with grandr, etc. But 12.04 worked great, so I live with 10.04 when I'm there. But now with 12.04 wounded, and I haven't been able to fix it, I may be looking at a reinstall, so now's the time to switch OSs, if I'm going to.
[18:32:21] <micges> atom1: ./linuxcnc from scripts diretory reported what version?
[18:32:29] <atom1> still compiling
[18:33:31] <atom1> tom@atom1:~/linuxcnc-dev/scripts$ ./linuxcnc
[18:33:31] <atom1> LINUXCNC - 2.7.0~pre2
[18:34:05] <atom1> but
[18:34:18] <atom1> when i ./scripts/rip-environment
[18:34:30] <atom1> i gettom@atom1:~/linuxcnc-dev$ linuxcnc
[18:34:30] <atom1> LINUXCNC - 2.5.4
[18:34:59] <micges> once again on what system you are ?
[18:35:09] <atom1> 10.04 ubuntu
[18:35:32] <atom1> normally running 2.5.4
[18:36:07] <micges> hmm env thing should work
[18:36:20] <atom1> apparently it isn't
[18:41:15] <atom1> if i give it the full path it seems to work
[18:42:40] <KimK> pcw_home: Oh, sorry, I misread your earlier line, I trust 14.04 has been working out OK for you? I'd still like to get away from Ubuntu (and Gnome) while those guys, as I think cradek said earlier, "...are out in the weeds..." If I thought I could get help if I needed it, instead of "why didn't you install wheezy?", I think I'd install Mint. I might anyway, lol.
[18:44:50] <atom1> ok it seems to be working ok now
[18:45:02] <atom1> dunno what i did the first time
[18:47:55] <atom1> now how do i get it to see my configs?
[18:48:58] <micges> rename ~/emc2 to ~/linuxcnc
[18:49:43] <atom1> it's already ~/linuxcnc
[18:50:25] <micges> you have configs there?
[18:50:39] <atom1> in a config folder yes
[18:50:55] <atom1> i've done this with 2.6 but forgot how i did it
[18:51:35] <micges> then it should work
[18:51:44] <atom1> ./home/tom/linuxcnc/configs/sherline
[18:54:06] <atom1> ok i got it
[18:58:54] <atom1> i thought i did anyway..
[19:17:05] <Tom_itx> thanks for the help
[19:19:50] <micges> np
[19:21:12] <KimK> Is anyone here using Wheezy? How's it working out?
[19:22:25] <micges> KimK: that's the one latest lcnc distro is based?
[19:23:20] <pcw_home> Wheezy works fine with my hardware testing (though the default GUI is pretty spartan)
[19:23:43] <KimK> I'm not sure, that's why I'm here asking questions. I've heard talk of it as a possible new LinuxCNC OS, though.
[19:24:08] <pcw_home> The latest ISO uses Wheezy
[19:25:34] <micges> pcw_home: default gui is LXDE? with cpu measurement in lower right?
[19:26:06] <pcw_home> Not sure what its called
[19:26:31] <micges> ok
[19:28:23] <KimK> pcw_home: OK, I'll install from that then, after I resize. In the past I've used Debian as the third OS in a multi-boot, so I'd have a tool in partition 3 to use when working with partitions 1 & 2, but I've never actually tried to run LinuxCNC on Debian.
[19:28:44] <KimK> micges: XFCE, maybe?
[19:28:56] <micges> KimK: it's stable, less config problems than ubuntu
[19:29:27] <micges> maybe
[19:29:51] <micges> I always switch to lxde when I can and I can
[19:30:05] <KimK> Yes, Ubuntu and Gnome are running people off left and right with their shenanigans, IMO.
[19:30:14] <micges> so I don't remember default one on iso
[19:31:20] <pcw_home> the default GUI editor (mousepad) is not as nice as gedit
[19:31:36] <KimK> micges: OK, thanks, I'll give LXDE a try, if they make it easy to do. And they probably do.
[19:32:02] <KimK> pcw_home: Did you fix it or live with it?
[19:32:39] <pcw_home> im still living with it, I guess I could install Gnome
[19:36:45] <KimK> Ha, I forgot about GNOMEedit, lol. That's why I was interested in Mint, because of Cinnamon and MATE (mah-TAY). Cinnamon tries to take Gnome 3 and fix it, which I thought was a good idea at first, now not sure. MATE takes Gnome 2 as it was in 10.04 (working great!) and forks it forward from there.
[19:38:39] <KimK> I've tried Cinnamon, it's OK, but has a few minor hiccups, most people won't be bothered. But I want to try MATE next, make sure I'm not missing out on something good. I always liked the 10.04 menu.
[19:41:51] <KimK> Mint 17.1 happens to be at the top of http://distrowatch.com right now.
[19:48:02] <KimK> The guys are probably right though, Debian is probably smaller/lighter and more standard than Mint.
[20:39:23] <Tom_itx> XFCE is default on the iso
[20:39:33] <Tom_itx> i have installed it on a spare ssd
[20:39:57] <Tom_itx> and i did install gedit as the editor
[21:01:51] <atom1> zlog,
[21:19:01] <KimK> Tom_itx: Do you recall how much more you had to install to get gedit back?
[21:22:51] <skunkworks> iirc all I did was do a sudo apt-get install gedit... it installed what was needed
[21:24:42] <atom1> yeah
[21:24:49] <atom1> only i did it from the package manager
[21:24:59] <atom1> i'm installing on the ssd with wheezy now
[21:25:08] <atom1> it's dealing me all sorts of fits
[21:25:26] <atom1> libmodbus-dev is installed and it's not liking that
[21:25:36] <cmorley> kimk: i'm not thrilled with wheezy but it may just be XFCE (i think that's what it is), on one computer I switch to MATE and like it alot. though I havent run it for too long.
[21:25:44] <atom1> libusb 1.0.0-dev is installed and it's not liking that either
[21:26:45] <atom1> error: libmodbus3 not found
[21:26:55] <atom1> it installed 5 and -dev
[21:28:48] <cmorley> KimK: I will try mint debian when the next version comes out soon. I would use mint17 if I could get linuxcnc to work on it.
[21:36:39] <KimK> cmorley: Hi! Good to hear from you. Interesting, you've tried Mint17 and couldn't get LinuxCNC to work on it? What happened?
[21:37:57] <cmorley> no I havent tried mint 17 yet, I tried 16 I think but I can't specifically remember y I didn't end up with it.
[21:39:27] <cmorley> though linux did run on it in simulator at least
[21:39:33] <cmorley> linuxcnc
[21:52:45] <KimK> I'm presently resizing my "Unit 1" in prep for the Wheezy install. Let me check on it... OK, it was done, started Wheezy install, I'll let you know how it went shortly. I'll have two other partitions, so one could be Mint17 MATE, and see how it gets along woth LinuxCNC. Maybe one for Ubuntu 14.04? Or what would you suggest?
[22:13:19] <seb_kuzminsky> we currently build on debian wheezy, ubuntu lucid (10.04), and ubuntu precise (12.04) on the buildbot all the time, so i'm confident those three distros work well
[22:13:48] <seb_kuzminsky> i bet the comparable version(s?) of mint should work well too, but i dont know what their version numbers are
[22:14:10] <atom1> i'm having issues compiling on wheezy right now
[22:14:18] <atom1> swapped to my ssd to try it
[22:14:41] <seb_kuzminsky> atom1: linuxcnc requires several packages to be installed in order to compile right
[22:14:58] <seb_kuzminsky> you can ask it for the list of required build-dependencies by running these commands:
[22:15:01] <atom1> yeah i know
[22:15:05] <seb_kuzminsky> ah ok
[22:15:10] <atom1> i installed modbus and it's still bitching
[22:15:11] <atom1> -dev
[22:15:26] <atom1> i installed libusb 1.0.0-dev and it didn't like that either
[22:15:55] <atom1> libmodbus3 and all i can get is libmodbus5 and -dev
[22:16:01] <seb_kuzminsky> i have libmodbus-dev version 3.0.3-1 on my wheezy machine and it's working well
[22:16:06] <atom1> libusb 1.0.0-dev is there and installed
[22:16:40] <seb_kuzminsky> http://paste.ubuntu.com/9324572/
[22:16:52] <KimK> Hi Seb, good to hear from you! You're a busy guy, are you managing 2.7 too? My Wheezy initial install is done, now downloading the first updates.
[22:17:14] <seb_kuzminsky> hi KimK, long time no hear :-)
[22:17:17] <seb_kuzminsky> hope you're well
[22:17:33] <seb_kuzminsky> atom1: i have libusb-1.0-0-dev version 2:1.0.11-1
[22:17:38] <KimK> Mostly, lol.
[22:17:43] <seb_kuzminsky> heh yeah
[22:18:10] <seb_kuzminsky> http://paste.ubuntu.com/9324585/
[22:18:31] <seb_kuzminsky> atom1: when you say "it doesn't like it", what exactly do you mean?
[22:19:08] <atom1> http://paste.debian.net/134377/
[22:19:26] <seb_kuzminsky> ok, that looks good
[22:19:38] <seb_kuzminsky> now what's the error? is it at configure-time or compile-time?
[22:19:43] <atom1> configure: error: libmodbus3 not found!
[22:19:43] <atom1> install with "sudo apt-get install libmodbus-dev" or disable with
[22:19:43] <atom1> "configure --without-libmodbus"
[22:19:56] <atom1> configure time
[22:20:10] <atom1> same with libusb 1.0.0-dev
[22:20:21] <seb_kuzminsky> paste your src/config.log
[22:21:17] <atom1> http://paste.debian.net/134378/
[22:22:01] <seb_kuzminsky> atom1: what do you get from 'uname -a'
[22:22:12] <KimK> Sorry I couldn't make it to Texas this summer, it sounded like fun. How big a crowd did you get there?
[22:22:18] <seb_kuzminsky> and 'lsb_release -ac'
[22:22:27] <atom1> Linux atom1 3.4-9-rtai-686-pae #1 SMP PREEMPT Debian 3.4.55-3linuxcnc i686 GNU/Linux
[22:22:38] <seb_kuzminsky> ok good
[22:22:50] <atom1> No LSB modules are available.
[22:22:50] <seb_kuzminsky> atom1: and dpkg-architecture
[22:22:50] <atom1> Distributor ID: Debian
[22:22:50] <atom1> Description: Debian GNU/Linux 7.7 (wheezy)
[22:22:50] <atom1> Release: 7.7
[22:22:50] <atom1> Codename: wheezy
[22:23:11] <atom1> not found
[22:23:35] <atom1> err command not found
[22:23:38] <seb_kuzminsky> KimK: Houston was great this year. It was Chris Radek and Jeff Epler and Jon Elson and me, and a bunch of new guys getting their systems configured and running
[22:23:52] <seb_kuzminsky> great fun, and, ahem, more productive than Witchita last year... ;-)
[22:24:05] <atom1> good to hear
[22:24:13] <seb_kuzminsky> atom1: it's in dpkg-dev
[22:26:45] <atom1> http://paste.debian.net/134379/
[22:27:03] <seb_kuzminsky> atom1: well that all looks good
[22:27:38] <seb_kuzminsky> hmm, let me try something here
[22:28:23] <cradek> don't forget john k
[22:28:29] <seb_kuzminsky> oh yeah!
[22:28:50] <seb_kuzminsky> he was helping the Tx/Rx hosts configure a few of their machines
[22:29:12] <seb_kuzminsky> one little tiny circuit board engraving machine, and one giant vertical mill with a tool changer
[22:29:21] <seb_kuzminsky> and cradek's little gantry-homing test machine
[22:29:28] <seb_kuzminsky> jmk's a wizard
[22:29:38] <atom1> where's he from?
[22:30:05] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff 92b7185 06linuxcnc 10src/hal/components/moveoff.comp moveoff.comp cleanups * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=92b7185
[22:30:06] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff fb9e2cf 06linuxcnc 10src/hal/components/moveoff.comp wip: next_state * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=fb9e2cf
[22:31:57] <seb_kuzminsky> atom1: he's from the planet zarquon
[22:32:03] <seb_kuzminsky> https://www.youtube.com/watch?v=rKwMcwfRuMw#t=110
[22:36:40] <skunkworks> is dewey a bot that listens to irc and creates/improves hal components?
[22:37:00] <Tom_itx> heh
[22:37:06] <seb_kuzminsky> he definitely is the second part of that ;-)
[22:37:16] <seb_kuzminsky> doesnt spend much time on irc though
[22:37:22] <seb_kuzminsky> too busy coding, i suppose ;-)
[22:38:15] <atom1> i'll pick this up tomorrow...
[22:38:16] <atom1> gnite
[22:38:31] <skunkworks> night
[22:39:17] <seb_kuzminsky> atom1, err, Tom_itx: what do you get from "pkg-config libmodbus --modversion"?
[22:39:22] <seb_kuzminsky> opos
[22:39:23] <seb_kuzminsky> oops
[22:40:51] <Tom_itx> oh crap... just shut it down
[22:41:12] <seb_kuzminsky> Tom_itx: there's something fishy going on, but i dont know what yet
[22:41:31] <Tom_itx> libmodbus shows 5 in package manager
[22:41:41] <seb_kuzminsky> that's fine
[22:42:18] <seb_kuzminsky> the package name is "libmodbus5", but the version is "3.0.3-1", right?
[22:42:31] <Tom_itx> i believe so yes
[22:42:44] <seb_kuzminsky> i wonder why configure isn't seeing it
[22:43:01] <Tom_itx> it's on a ssd but i haven't had any problems with it
[22:43:27] <seb_kuzminsky> yeah, that shouldnt matter
[22:44:37] <KGB-linuxcnc> 03Dewey Garrett 05dgarr/moveoff a2a63b6 06linuxcnc moveoff.comp: merge local work-in-progress * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=a2a63b6
[22:48:28] <seb_kuzminsky> Tom_itx: if you're worried about filesystem corruption, you can use "debsums libmodbus5 libmodbus-dev" to verify those packages
[22:50:22] <seb_kuzminsky> Tom_itx: i know you said you know about the build-dependency checking step, but
[22:50:36] <seb_kuzminsky> if you're missing pkg-config, that could explain the behavior you see
[22:51:33] <seb_kuzminsky> huh, i see now that we *don't* build-depend on pkg-config, even though we use it in configure...
[22:51:38] <seb_kuzminsky> that's kind of bogus
[22:51:55] <seb_kuzminsky> i guess we have been getting lucky and one of the libs we *do* build-depend on pulls it in
[22:53:31] <seb_kuzminsky> Tom_itx: would you humour me and paste the output of dpkg-checkbuilddeps next time you have your atom1 box up?
[22:54:25] <seb_kuzminsky> on wheezy, tk8.5-dev pulls in pkg-config
[22:55:47] <seb_kuzminsky> as does libgtk2.0-dev
[22:55:50] <seb_kuzminsky> and maybe others
[22:57:02] <seb_kuzminsky> Tom_itx: as per the outdated instructions here: http://wiki.linuxcnc.org/cgi-bin/wiki.pl?Installing_LinuxCNC#Resolving_outstanding_build_dependencies
[22:57:13] <seb_kuzminsky> it's "configure uspace" now, not "configure sim"
[22:58:05] <seb_kuzminsky> i guess that means those building instructions should live in the git repo, so they can match the branch they're for, and be part of the asciidocs
[22:59:26] <KimK> I also noticed that when I did the updates, when I highlighted any of the stuff from LinuxCNC, it didn't do anything (i.e., say "this source does not support changelogs", or some such). On the other hand, highlighting the Debian items said "can't find information"(?) or something similar, so maybe it's a case of too many bugs at once, lol. Anyway, now you know.
[23:00:02] <seb_kuzminsky> heh
[23:00:11] <seb_kuzminsky> i'm not sure what i know now :-)
[23:00:20] <KimK> Ha
[23:00:37] <seb_kuzminsky> i know the buildbot and the deb archive at wlo do not support changelogs
[23:02:23] <KimK> Speaking of buildbot, I noticed that there are four buildbot-related items in the software sources, two source and two binaries. I imagine that was your doing, any advice for us?
[23:03:02] <KimK> None were enabled by default
[23:03:19] <seb_kuzminsky> is this in an install from the binary.hybrid.iso? if so it's cradek's fault ;-)
[23:03:36] <seb_kuzminsky> it's deliberate and right that the buildbot deb-sources not be enabled by default
[23:03:48] <seb_kuzminsky> most users are better off just using the official releases from wlo
[23:03:49] <KimK> Yes, this is on the Wheezy/2.6 "hybrid ISO"
[23:04:07] <seb_kuzminsky> maybe there's one source for 2.6 and one for master? (and one for binary and one for source packages?)
[23:04:18] <KimK> That sounds right
[23:04:45] <Tom_itx> !bookmark..
[23:04:50] <Tom_itx> i'll check in the AM
[23:05:01] <KimK> It's probably a forehead-slapper, but what's wlo?
[23:05:11] <seb_kuzminsky> www.linuxcnc.org
[23:05:16] <seb_kuzminsky> i'm a lazy typer
[23:05:23] <KimK> Ha! OK
[23:06:06] <KimK> You could be even lazier: lo
[23:06:20] <KimK> Funny
[23:06:58] <KimK> What would somebody do with the buildbot sources though, if they were adventurous?
[23:07:04] <seb_kuzminsky> we sometimes refer to git.linuxcnc.org as glo"
[23:07:20] <seb_kuzminsky> so "lo" would be ambiguous
[23:07:25] <seb_kuzminsky> *even more ambiguous
[23:07:59] <seb_kuzminsky> KimK: you could "apt-get source linuxcnc" to fetch the source package and get exactly what we built the official binary package from
[23:08:28] * KimK puts "shoe" back on shelf so as to not make things even *more* ambiguous.
[23:09:00] <KimK> Oh, OK, well, I was thinking of the buildbot stuff specifically.
[23:09:05] <seb_kuzminsky> it was important before everyone switched to git, and it's probably important still for legal reasons i dont really understand
[23:09:23] <seb_kuzminsky> oh, i misunderstood your question
[23:09:36] <seb_kuzminsky> you're asking "what would a user do with the buildbot apt sources"
[23:09:59] <KimK> Yes, exactly (even if not a typical user)
[23:10:03] <seb_kuzminsky> well, they could enable them to get binary packages of commits in between official releases
[23:10:48] <seb_kuzminsky> currently there latest 2.6 release is 2.6.4, but there have been 20 commits to the 2.6 branch since that release was made
[23:11:35] <KimK> So then "we" would be running at our homes the same buildbots that you're running?
[23:12:00] <seb_kuzminsky> those 20 actually includes some bugfixes, so i'm tardy in releasing 2.6.5...
[23:12:26] <seb_kuzminsky> but yeah, if a user enabled the buildbot source in their apt list, then they would get automatic updates of the linuxcnc package any time a new commit goes into 2.6
[23:12:38] <seb_kuzminsky> sometimes that's good (like when a bug is fixed or documentation is improved)
[23:12:54] <seb_kuzminsky> sometimes (hopefully rarely) that's bad (like when a new bug gets introduced)
[23:13:21] <KimK> Ha, please take your time releasing 2.6.5, if 2.7 is in the wings, let's make the "last"(?) 2.6 a good one.
[23:13:54] <seb_kuzminsky> i intend to keep supporting 2.6 with bugfix releases for a while after 2.7.0 is released, so there's some overlap for folks who are slow in upgrading
[23:14:05] <seb_kuzminsky> 2.7's a ways out still...
[23:14:13] <KimK> That's great, thanks.
[23:14:45] <seb_kuzminsky> sure :)
[23:19:21] <KimK> Must reboot, BBIAB
[23:27:23] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 3da6a61 06linuxcnc 10src/hal/user_comps/gs2_vfd.c gs2_vfd: accept -g to turn on debug output * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=3da6a61
[23:31:53] <KGB-linuxcnc> 03Sebastian Kuzminsky 052.6 090bf29 06linuxcnc 10src/hal/user_comps/gs2_vfd.c gs2_vfd: add missing -A, -D, and -R command-line args * 14http://git.linuxcnc.org/?p=linuxcnc.git;a=commitdiff;h=090bf29