Re: [Emc-developers] Who changed the requiered python version?

[schoone...@btinternet.com]

Just checking the first box in 'make menuconfig' for building a 64 bit 
kernel will be enough.

My configs disable various 'features' I don't want, like suspend to RAM 
/ disk etc so may not be what you require.

regards

On 02/01/2016 20:04, emc-developers-requ...@lists.sourceforge.net wrote:
> Tahnks for the hint, I just checked on that and it seems that the named
> .config is for an x86 kernel,
> So I have to walk through the xconfig stuff without understandig waht I
> do, or...


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[Niemand Sonst]

I got nearly the same on my machine, I just changed the commands to use 
the default g++

$ lsb_release  -cr
Release:10.04
Codename:   lucid

$ g++ -v
Using built-in specs.
Target: i486-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
4.4.3-4ubuntu5.1' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs  
--enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared 
--enable-multiarch --enable-linker-build-id --with-system-zlib 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 --enable-nls 
--enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin --enable-objc-gc 
--enable-targets=all --disable-werror --with-arch-32=i486 --with-tune=generic 
--enable-checking=release --build=i486-linux-gnu --host=i486-linux-gnu 
--target=i486-linux-gnu
Thread model: posix
gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)

$ cat nbi.cc
#include 
const auto i = std::nearbyint(3.14);


$ g++ -std=c++0x -c nbi.cc && echo success
success

I have done that within the python 2.7 environment and with rip-environment
So I do not understand why I get the error during make with master, but 
not with 2.7

Norbert


Am 02.01.2016 um 23:03 schrieb Jeff Epler:
> $ lsb_release  -cr
> Release:10.04
> Codename:   lucid
> $ g++-4.4 -v
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
> 4.4.3-4ubuntu5.1' --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs  
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --enable-shared 
> --enable-multiarch --enable-linker-build-id --with-system-zlib 
> --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
> --with-gxx-include-dir=/usr/include/c++/4.4 --program-suffix=-4.4 
> --enable-nls --enable-clocale=gnu --enable-libstdcxx-debug --enable-plugin 
> --enable-objc-gc --enable-targets=all --disable-werror --with-arch-32=i486 
> --with-tune=generic --enable-checking=release --build=i486-linux-gnu 
> --host=i486-linux-gnu --target=i486-linux-gnu
> Thread model: posix
> gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
> $ cat nbi.cc
> #include 
> const auto i = std::nearbyint(3.14);
> $ g++-4.4 -std=c++0x -c nbi.cc && echo success
> success


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[EBo]

My guess is that the environment is different between when it is 
compiling and at your desktop, and may be a pain to find.  Try 
copy/pasting the line that is failing during the build and see if that 
will work.  I doubt that it is "g++-4.4 -std=c++0x -c nbi.cc && echo 
success".  This will let you know if there another problem (like 
std=c++0x not being set, or possibly the error being on a different line 
of code).

Just a thought.

   EBo --

On Jan 3 2016 4:01 AM, Niemand Sonst wrote:
> I got nearly the same on my machine, I just changed the commands to 
> use
> the default g++
>
> $ lsb_release  -cr
> Release:10.04
> Codename:   lucid
>
> $ g++ -v
> Using built-in specs.
> Target: i486-linux-gnu
> Configured with: ../src/configure -v --with-pkgversion='Ubuntu
> 4.4.3-4ubuntu5.1'
> --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs
> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr
> --enable-shared --enable-multiarch --enable-linker-build-id
> --with-system-zlib --libexecdir=/usr/lib --without-included-gettext
> --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4
> --program-suffix=-4.4 --enable-nls --enable-clocale=gnu
> --enable-libstdcxx-debug --enable-plugin --enable-objc-gc
> --enable-targets=all --disable-werror --with-arch-32=i486
> --with-tune=generic --enable-checking=release --build=i486-linux-gnu
> --host=i486-linux-gnu --target=i486-linux-gnu
> Thread model: posix
> gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
>
> $ cat nbi.cc
> #include 
> const auto i = std::nearbyint(3.14);
>
>
> $ g++ -std=c++0x -c nbi.cc && echo success
> success
>
> I have done that within the python 2.7 environment and with 
> rip-environment
> So I do not understand why I get the error during make with master, 
> but
> not with 2.7
>
> Norbert
>
>
> Am 02.01.2016 um 23:03 schrieb Jeff Epler:
>> $ lsb_release  -cr
>> Release:10.04
>> Codename:   lucid
>> $ g++-4.4 -v
>> Using built-in specs.
>> Target: i486-linux-gnu
>> Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
>> 4.4.3-4ubuntu5.1' 
>> --with-bugurl=file:///usr/share/doc/gcc-4.4/README.Bugs  
>> --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr 
>> --enable-shared --enable-multiarch --enable-linker-build-id 
>> --with-system-zlib --libexecdir=/usr/lib --without-included-gettext 
>> --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.4 
>> --program-suffix=-4.4 --enable-nls --enable-clocale=gnu 
>> --enable-libstdcxx-debug --enable-plugin --enable-objc-gc 
>> --enable-targets=all --disable-werror --with-arch-32=i486 
>> --with-tune=generic --enable-checking=release --build=i486-linux-gnu 
>> --host=i486-linux-gnu --target=i486-linux-gnu
>> Thread model: posix
>> gcc version 4.4.3 (Ubuntu 4.4.3-4ubuntu5.1)
>> $ cat nbi.cc
>> #include 
>> const auto i = std::nearbyint(3.14);
>> $ g++-4.4 -std=c++0x -c nbi.cc && echo success
>> success
>
>
> 
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[EBo]

On Jan 2 2016 7:23 PM, Gene Heskett wrote:
> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>
>> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>> >> I am sorry you purchased defective hardware.  You should consider
>> >> returning it for a refund if you still can.
>> >
>> > The hardware is not defect, it is just new and does what it is
>> > suposed to do.
>>
>> It is broken by design, but it is still broken.
>
> I am with Andy. It may be by design, but its still broken, return it 
> and
> insist on getting something that does work.  The one sure way to get
> those nitwits attention is to bounce the product back at them for a
> refund.

While I have to agree with Andy about the brokenness of OS locked Bios, 
I have also found that it is as likely they will refuse the return 
because you did something unexpected/non-standard to it.  If you can 
return it and get a different one.  If you cannot, then complain all 
over the place -- bad PR is something that chips away a little by little 
at this typ of crap.  Also, take a look at the low end Sager/Clevo 
laptops.  There are companies which configure them with linux installed. 
I use high end versions of these at work and home.

   EBo --


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[Niemand Sonst]

So again, the notebook does not Block the install of other OS!!!

I installed
- Windows 7
- Windows 8.1
- Debian 8.2 amd64 (twice)

and I can boot also from:
- Clonezilla
- Boot repair disk
- Linux Mint Live

So it is OK!

Just Linuxcnc ISO is 32-bit and therefor not suited!

I am satisfied with the hardware, it has good design, is powerfull and I 
got it at a resonable price (€ 699)

IHMO not the Laptop is wrong, but we will have to see how linuxcnc will 
handle modern hardware in the future.


@EBo
I just llog for a Sager/Clevo notebook and the new ones do have UEFI 
Bios like my one  ;-)

Norbert


Am 03.01.2016 um 12:02 schrieb EBo:
> On Jan 2 2016 7:23 PM, Gene Heskett wrote:
>> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>>
>>> On 2 January 2016 at 16:04, Niemand Sonst  wrote:
> I am sorry you purchased defective hardware.  You should consider
> returning it for a refund if you still can.
 The hardware is not defect, it is just new and does what it is
 suposed to do.
>>> It is broken by design, but it is still broken.
>> I am with Andy. It may be by design, but its still broken, return it
>> and
>> insist on getting something that does work.  The one sure way to get
>> those nitwits attention is to bounce the product back at them for a
>> refund.
> While I have to agree with Andy about the brokenness of OS locked Bios,
> I have also found that it is as likely they will refuse the return
> because you did something unexpected/non-standard to it.  If you can
> return it and get a different one.  If you cannot, then complain all
> over the place -- bad PR is something that chips away a little by little
> at this typ of crap.  Also, take a look at the low end Sager/Clevo
> laptops.  There are companies which configure them with linux installed.
> I use high end versions of these at work and home.
>
> EBo --
>
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[EBo]

On Jan 3 2016 5:42 AM, Niemand Sonst wrote:
> Am 03.01.2016 um 12:08 schrieb EBo:
>> "g++-4.4 -std=c++0x -c nbi.cc && echo
>> success"
> Is working fine on a terminal.

OK.  But when you are compiling whatever code has the nearbyint in it, 
what is the full command line to compile that?  Can you copy/paste the 
exact error?  You may have done it before, but I have deleted all the 
email chain.

   EBo --


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[Niemand Sonst]

..
Compiling emc/usr_intf/xemc.cc
Linking xlinuxcnc
Compiling emc/task/emcsvr.cc
Linking linuxcncsvr
Compiling emc/motion/emcmotglb.c
Compiling emc/task/emctask.cc
In file included from emc/rs274ngc/rs274ngc_interp.hh:20,
   from emc/task/emctask.cc:29:
emc/rs274ngc/interp_internal.hh: In function ‘int round_to_int(T)’:
emc/rs274ngc/interp_internal.hh:44: error: ‘nearbyint’ is not a member
of ‘std’
make: *** [objects/emc/task/emctask.o] Fehler 1
.

I know there was a flag I can put to get more debug information, but I do not 
remember waht it was.

Norbert



Am 03.01.2016 um 14:10 schrieb EBo:
> On Jan 3 2016 5:42 AM, Niemand Sonst wrote:
>> Am 03.01.2016 um 12:08 schrieb EBo:
>>> "g++-4.4 -std=c++0x -c nbi.cc && echo
>>> success"
>> Is working fine on a terminal.
> OK.  But when you are compiling whatever code has the nearbyint in it,
> what is the full command line to compile that?  Can you copy/paste the
> exact error?  You may have done it before, but I have deleted all the
> email chain.
>
> EBo --
>
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[Niemand Sonst]

Am 03.01.2016 um 12:08 schrieb EBo:
> "g++-4.4 -std=c++0x -c nbi.cc && echo
> success"
Is working fine on a terminal.

Norbert

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Who changed the requiered python version?

[EBo]

@Norbert

the Sager/Clevo notebook are suported for Linux, so if you have a 
problem they, unlike Best Buy, do not try to claim that I violated the 
warranty by installing Linux.

On Jan 3 2016 5:40 AM, Niemand Sonst wrote:
> So again, the notebook does not Block the install of other OS!!!
>
> I installed
> - Windows 7
> - Windows 8.1
> - Debian 8.2 amd64 (twice)
>
> and I can boot also from:
> - Clonezilla
> - Boot repair disk
> - Linux Mint Live
>
> So it is OK!
>
> Just Linuxcnc ISO is 32-bit and therefor not suited!
>
> I am satisfied with the hardware, it has good design, is powerfull 
> and I
> got it at a resonable price (€ 699)
>
> IHMO not the Laptop is wrong, but we will have to see how linuxcnc 
> will
> handle modern hardware in the future.
>
>
> @EBo
> I just llog for a Sager/Clevo notebook and the new ones do have UEFI
> Bios like my one  ;-)
>
> Norbert
>
>
> Am 03.01.2016 um 12:02 schrieb EBo:
>> On Jan 2 2016 7:23 PM, Gene Heskett wrote:
>>> On Saturday 02 January 2016 12:08:19 andy pugh wrote:
>>>
 On 2 January 2016 at 16:04, Niemand Sonst  wrote:
>> I am sorry you purchased defective hardware.  You should 
>> consider
>> returning it for a refund if you still can.
> The hardware is not defect, it is just new and does what it is
> suposed to do.
 It is broken by design, but it is still broken.
>>> I am with Andy. It may be by design, but its still broken, return 
>>> it
>>> and
>>> insist on getting something that does work.  The one sure way to 
>>> get
>>> those nitwits attention is to bounce the product back at them for a
>>> refund.
>> While I have to agree with Andy about the brokenness of OS locked 
>> Bios,
>> I have also found that it is as likely they will refuse the return
>> because you did something unexpected/non-standard to it.  If you can
>> return it and get a different one.  If you cannot, then complain all
>> over the place -- bad PR is something that chips away a little by 
>> little
>> at this typ of crap.  Also, take a look at the low end Sager/Clevo
>> laptops.  There are companies which configure them with linux 
>> installed.
>> I use high end versions of these at work and home.
>>
>> EBo --
>>
>>
>> 
>> --
>> ___
>> Emc-developers mailing list
>> Emc-developers@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>>
>
>
> 
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

[Emc-developers] Difference RTAI 5.0 <--> PREEMPT-rt ?

[Karlsson & Wang]

Do anybode know the difference between RTAI and PREEMPT-rt?

Regards Nicklas Karlsson

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Difference RTAI 5.0 <--> PREEMPT-rt ?

[Niemand Sonst]

Yes,

in some words:

RTAI is much faster, but relies on the kernel you have, so it is much 
more complicated to be included in software parts.
It is mostly needed only for very high speed applications

PREEMPT-RT is a a little bit slower than RTAI, but can be implemented in 
software much easier, just imagine it is a modul.

That is very simple explained, there are more differences. For a normal 
CNC opperation both should work fine. But if you use i.e. software 
stepgenerator over a LPT, than take the RTAI.

Norbert

Am 03.01.2016 um 19:06 schrieb Karlsson & Wang:
> Do anybode know the difference between RTAI and PREEMPT-rt?
>
> Regards Nicklas Karlsson
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Difference RTAI 5.0 <--> PREEMPT-rt ?

[Neil Whelchel]

Hello,
To cut to the core, RTAI is basically an interrupt dispatcher that traps
interrupts and re-routes them up either through the RTAI (realtime)
modules, or for non realtime tasks back to the Linux kernel. RTAI also
provides an API for realtime functions, and floating point operations.
The general intent is to run realtime processes in the kernel.
PREEMPT-RT is a configuration option for the kernel to add preemption to
many more places in the kernel, in particular, it makes the spinlocks
preemptable, and it adds a priority tree (priority inheritance). It also
includes changes to the high resolution timer code. It does not introduce
any API, however all timers in user code are replaced with high resolution
timers. There are some issues with PREEMPT-RT and the VGA text console that
have not yet been corrected. (Anything that writes to the VGA text console
such as printk() introduce large unpredictable latencies.) This patch is
intended to run realtime processes in user space, but it also allows
realtime kernel modules to be used.
-Neil-



On Sun, Jan 3, 2016 at 10:06 AM, Karlsson & Wang <
nicklas.karls...@karlssonwang.se> wrote:

> Do anybode know the difference between RTAI and PREEMPT-rt?
>
> Regards Nicklas Karlsson
>
>
> --
> ___
> Emc-developers mailing list
> Emc-developers@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Difference RTAI 5.0 <--> PREEMPT-rt ?

[Peter C. Wallace]

On Sun, 3 Jan 2016, Niemand Sonst wrote:

> Date: Sun, 3 Jan 2016 19:59:41 +0100
> From: Niemand Sonst 
> Reply-To: EMC developers 
> To: EMC developers 
> Subject: Re: [Emc-developers] Difference RTAI 5.0 <--> PREEMPT-rt ?
> 
> Yes,
>
> in some words:
>
> RTAI is much faster, but relies on the kernel you have, so it is much
> more complicated to be included in software parts.
> It is mostly needed only for very high speed applications
>
> PREEMPT-RT is a a little bit slower than RTAI, but can be implemented in
> software much easier, just imagine it is a modul.
>
> That is very simple explained, there are more differences. For a normal
> CNC opperation both should work fine. But if you use i.e. software
> stepgenerator over a LPT, than take the RTAI.
>
> Norbert

Depending on the hardware the differences between RTAI and Preempt-RT may be 
minimal:

http://freeby.mesanet.com/g3258-rtai.png
http://freeby.mesanet.com/h97-g3258-preemt-rt.png

Both about 1/2 a day of YouTube videos (I favor the crackling fireplace ones) 
and 10 glxgears each

I'll try some Skylake hardware when I can figure out how to build the latest 
(4.4-rc6-rt1) Preempt-RT kernel

Note that both the latency test and latency histogram mainly display 
_dispatch_ latency. Actual latency to _do_ anything (allocate memory, do I/O, 
access the PCI bus, etc) will be significantly worse


Peter Wallace
Mesa Electronics


--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers

Re: [Emc-developers] Error during make

[Jeff Epler]

use make V=1 to print the commands as they are executed.

Hm, in my example program I made sure to include , but 
isn't included in rs274ngc_interp.hh.

I just pushed this change to master branch which may fix it:

commit 18517a3ee9cffe35a27c12d14b314e77794459aa
Author: Jeff Epler 
Date:   Sun Jan 3 13:54:04 2016 -0600

task: include  for std::nearbyint

Signed-off-by: Jeff Epler 

diff --git a/src/emc/rs274ngc/interp_internal.hh 
b/src/emc/rs274ngc/interp_internal.hh
index 6df90b1..f2eb3a9 100644
--- a/src/emc/rs274ngc/interp_internal.hh
+++ b/src/emc/rs274ngc/interp_internal.hh
@@ -24,6 +24,7 @@
 #include "emcpos.h"
 #include "libintl.h"
 #include 
+#include 
 
 
 #define _(s) gettext(s)

--
___
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers