On Wed, 28 Nov 2018 at 23:20, Alec Ari wrote:
> LinuxCNC being passed the wrong ./configure option shouldn't cause the
> result it did. A NULL pointer deference is never an appropriate method of
> informing the user that something is wrong in their configure line. Please
> do not accept this as
LinuxCNC being passed the wrong ./configure option shouldn't cause the result
it did. A NULL pointer deference is never an appropriate method of informing
the user that something is wrong in their configure line. Please do not accept
this as the appropriate behavior.
Alec
On Wednesday 28 November 2018 12:15:25 Jon Elson wrote:
> On 11/28/2018 07:23 AM, Jeff Epler wrote:
> > .. which is likely, in turn, to affect LinuxCNC. Those
> > interested
> > should look at modernizing the parts of LinuxCNC that
> > still use gtk2.
> >
> > I know this still includes halscope
Hello,
I would prefer addressing this problem on the public mailing list. I do not
mind anyone contacting me directly. The version of RTAI the LinuxCNC developers
are using is a depreciated fork of RTAI 3, which is also depreciated upstream.
NULL pointer deference bugs is usually caused by an
On 11/28/2018 07:23 AM, Jeff Epler wrote:
.. which is likely, in turn, to affect LinuxCNC. Those
interested
should look at modernizing the parts of LinuxCNC that
still use gtk2.
I know this still includes halscope and halmeter. it
would be a real
pity to lose halscope to CADTs^Wthe
On Wednesday 28 November 2018 08:23:52 Jeff Epler wrote:
> .. which is likely, in turn, to affect LinuxCNC. Those interested
> should look at modernizing the parts of LinuxCNC that still use gtk2.
>
> I know this still includes halscope and halmeter. it would be a real
> pity to lose halscope
On Wed, 28 Nov 2018 at 10:26, theman whosoldtheworld
wrote:
> [EMC] NML_FILE = emc.nml
>
> these row in file.ini is still valid?
Some sections of code still look for it:
https://github.com/LinuxCNC/linuxcnc/search?l=C%2B%2B=NML_FILE
No version of the docs (back to 2.2 at least) has ever
On Wed, 28 Nov 2018 at 13:25, Jeff Epler wrote:
> .. which is likely, in turn, to affect LinuxCNC. Those interested
> should look at modernizing the parts of LinuxCNC that still use gtk2.
>
The absolute lack of support on the pygtk mailing lists and IRC make me not
so upset with the idea of
.. which is likely, in turn, to affect LinuxCNC. Those interested
should look at modernizing the parts of LinuxCNC that still use gtk2.
I know this still includes halscope and halmeter. it would be a real
pity to lose halscope to CADTs^Wthe progress of the Linux desktop.
- Forwarded
[EMC] NML_FILE = emc.nml
these row in file.ini is still valid? because in html doc there is nothing
about, and in my sim config I'm not able to have response from these row
emcStatusBuffer = new RCS_STAT_CHANNEL(emcFormat, "emcStatus", "xemc",
EMC_NMLFILE);
because no EMC_NMLFILE is open
10 matches
Mail list logo
