Complete HOW-TO Linux Mint 18.1 32/64 RTAI or PREEMPT with RIP install or deb

I see yes i need to be in that folder hence cd src.

I ok now i am getting the same problem i had before (reinstalling everything). My dependencies were good and now they are not.
what did i do wrong?

elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ cd debian
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/debian $ ./configure uspace
successfully configured for 'uspace-LinuxMint-18.1'-'uspace+xenomai'..
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/debian $ cd ..
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ dpkg-checkbuilddeps
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ linuxcnc-dev/src
bash: linuxcnc-dev/src: No such file or directory
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ git checkout 2.7
Branch 2.7 set up to track remote branch 2.7 from origin.
Switched to a new branch '2.7'
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ linuxcnc-dev/src
bash: linuxcnc-dev/src: No such file or directory
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ cd ..
elroy@elroy-Lenovo-V570 ~ $ linuxcnc-dev/src
bash: linuxcnc-dev/src: Is a directory
elroy@elroy-Lenovo-V570 ~ $ cd debian
bash: cd: debian: No such file or directory
elroy@elroy-Lenovo-V570 ~ $ cd linuxcnc-dev
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ linuxcnc-dev/src
bash: linuxcnc-dev/src: No such file or directory
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ cd src
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/src $ linuxcnc-dev/src
bash: linuxcnc-dev/src: No such file or directory
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/src $ ../debian/configure uspace ; debuild -uc -us
unknown distribution: LinuxMint-18.1
configuration may be wrong!
successfully configured for 'uspace-LinuxMint-18.1'-'uspace'..
dpkg-buildpackage -rfakeroot -D -us -uc
dpkg-buildpackage: source package linuxcnc
dpkg-buildpackage: source version 1:2.7.8
dpkg-buildpackage: source distribution unstable
dpkg-buildpackage: source changed by Sebastian Kuzminsky <This email address is being protected from spambots. You need JavaScript enabled to view it.>
dpkg-source --before-build linuxcnc-dev
dpkg-buildpackage: host architecture i386
dpkg-checkbuilddeps: error: Unmet build dependencies: libgnomeprintui2.2-dev python-support tcl8.4-dev tk8.4-dev
dpkg-buildpackage: warning: build dependencies/conflicts unsatisfied; aborting
dpkg-buildpackage: warning: (Use -d flag to override.)
debuild: fatal error at line 1376:
dpkg-buildpackage -rfakeroot -D -us -uc failed
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/src $ dpkg-checkbuilddeps
dpkg-checkbuilddeps: error: cannot read debian/control: No such file or directory
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev/src $ cd ..
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $ dpkg-checkbuilddeps
dpkg-checkbuilddeps: error: Unmet build dependencies: libgnomeprintui2.2-dev python-support tcl8.4-dev tk8.4-dev
elroy@elroy-Lenovo-V570 ~/linuxcnc-dev $

Elroy try this command and report what happens please.

I just checked to make sure your dependencies are in this repository; this will get you going. Let me know how it goes.

Tutorial has been further clarified with the common dependency issues discussed here. I have also added git as a initial dependency install.

Unfortunately I can only have so many links or pictures in the forum or I would have a lot of pictures to help make this easier.. I wonder if there are exceptions to the forums rules that can be applied separately to individual members?

Andy or JT do you know if I could get an exception from the posting limits applied in this forum concerning links and images?

Everyone please feel free to suggest additions or clarification.

Tommy I completely understand, I get frustrated on the same topics and explanations too!
However I did have about 10 pages discussing these same issues again and again!

Thank you for your support and your help Tommy.

So I added this to each posting including the main post... The information was there but I made it bullet proof.. I think!


Commonly reported dependency:

dpkg-checkbuilddeps: error: Unmet build dependencies: libgnomeprintui2.2-dev python-support tcl8.4-dev tk8.4-dev

To fix the issue above please issue this code:
Regards,

James

Cncnoob1979,

I really appreciate your help. I get that you already told me how to get the dependencies. I wasn't very clear. I was trying to find out what i did wrong not what to do.

Tommylight,

Look i get your fustration. I know the tutorial is good. Please read my posts more throughly. I said that i must misunderstand something or the turtorial was missing something. That was not a jab at the tutorial. And it ended up being that i misunderstood. The tutorial has all the command stuff you need to execute in grey. I didn't realize that it was now saying be in this directory. I apologize for not being so clear. New and trying.

The problem with the forum is it's difficult to relay a conversation. So it's easy to be frustrated. But we can't read minds nor can others read ours. We're all human and get frustrated because of it.

Now enough of all that!

Elroy did you get it working for you?
Your issue that I could tell was the understanding of what step you were on.

You have to be in the source directory for the step you were on. Building LinuxCNC.

In the Debian directory is where you configure it (it's running Debian scripting)

Those are the two basic concepts hope that helps.

If you get stuck on a step - don't bypass it. It will not work generally speaking.

Try to figure out if your doing the right thing. A basic Linux command explanation is available widely on the net. If you're not familiar with it - no problem you can ask when or if you get stuck.

Edit: if it's my phrasing that confused you - let me know I'll try to reword it.

I already reworded the folder/command issue confusion, you pointed out.

I ok now i am getting the same problem i had before (reinstalling everything). My dependencies were good and now they are not.
what did i do wrong?

Seems it did not catch the dependency. Seems like a glitch in the "matrix" lol

In that step you did nothing wrong. As far as I can tell it seems you just confused where I was trying to point out what folder to be in. That could have been put different and I hopefully changed it to where no one else will confuse my intention.