emc-developers Mailing List for LinuxCNC

Processing commands for co...@bu...:

> tags 1080668 + fixed-upstream
Bug #1080668 [src:linuxcnc] Missing Build-Depends on python3-setuptools
Added tag(s) fixed-upstream.
> forwarded 1080668 https://github.com/LinuxCNC/linuxcnc/pull/3158
Bug #1080668 [src:linuxcnc] Missing Build-Depends on python3-setuptools
Set Bug forwarded-to-address to 'https://github.com/LinuxCNC/linuxcnc/pull/3158'.
> tags 1079419 + fixed-upstream
Bug #1079419 [linuxcnc-uspace] linuxcnc-uspace: please migrate from deprecated gtksourceview3 to gtksourceview4 (or 5)
Added tag(s) fixed-upstream.
> forwarded 1079419 https://github.com/LinuxCNC/linuxcnc/pull/3083
Bug #1079419 [linuxcnc-uspace] linuxcnc-uspace: please migrate from deprecated gtksourceview3 to gtksourceview4 (or 5)
Set Bug forwarded-to-address to 'https://github.com/LinuxCNC/linuxcnc/pull/3083'.
> tags 1085669 + fixed-upstream
Bug #1085669 [src:linuxcnc] linuxcnc: Python SyntaxWarning
Added tag(s) fixed-upstream.
> forwarded 1085669 https://github.com/LinuxCNC/linuxcnc/pull/3172
Bug #1085669 [src:linuxcnc] linuxcnc: Python SyntaxWarning
Set Bug forwarded-to-address to 'https://github.com/LinuxCNC/linuxcnc/pull/3172'.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
1079419: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1079419
1080668: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1080668
1085669: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1085669
Debian Bug Tracking System
Contact ow...@bu... with problems

thx Andy

tomp

On 11/2/24 07:41, andy pugh wrote:
> On Wed, 30 Oct 2024 at 16:11, Thomas J Powderly <tj...@gm...> wrote:
>
>> (http://www.hcnc.sk/ponuka.html and mailing list)
>>
>> show an interesting user interface
>>
>> It uses axis tabs to hold a background image of a task.
>>
>> The image is an isometric drawing of a job to be cut.
>>
>> The image is overlaid with  tcl numeric entries.
> This seems very similar in principle (and in execution) to my lathe macros:
> https://forum.linuxcnc.org/41-guis/26550-lathe-macros?start=240#247195
>
> And, in fact, it is just a case of editing/creating the SVG files and
> adding the buttons to each tab to make this work for milling (or any
> other machine)
> This post includes instructions on how to make your own cycles and
> graphics (including the rather hacky way that the numeric entry boxes
> are positioned by data hidden in the XML of their tooltip)
>
> Note that the lathe macros are included in one of the Gmoccapy sample
> configs - sim/gmoccapy/lathe_configs/lathe_macros
>

On Wed, 30 Oct 2024 at 16:11, Thomas J Powderly <tj...@gm...> wrote:

> (http://www.hcnc.sk/ponuka.html and mailing list)
>
> show an interesting user interface
>
> It uses axis tabs to hold a background image of a task.
>
> The image is an isometric drawing of a job to be cut.
>
> The image is overlaid with  tcl numeric entries.

This seems very similar in principle (and in execution) to my lathe macros:
https://forum.linuxcnc.org/41-guis/26550-lathe-macros?start=240#247195

And, in fact, it is just a case of editing/creating the SVG files and
adding the buttons to each tab to make this work for milling (or any
other machine)
This post includes instructions on how to make your own cycles and
graphics (including the rather hacky way that the numeric entry boxes
are positioned by data hidden in the XML of their tooltip)

Note that the lathe macros are included in one of the Gmoccapy sample
configs - sim/gmoccapy/lathe_configs/lathe_macros

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

I think the screenshots

(http://www.hcnc.sk/ponuka.html and mailing list)

show an interesting user interface


It uses axis tabs to hold a background image of a task.

The image is an isometric drawing of a job to be cut.

The image is overlaid with  tcl numeric entries.

Dimensions on the image have names ( APT like).

These number values are passed to an

ngc file that has named variables and uses o-words.


The method is a user friendly super-macro.

(the numbers and the program make a visual parametric system )


This idea is handy for work that varies just a little each eun.

An operator can adjust the program within constraints.


I think the idea is clever and useful.


One screen shot appears to show a wooden door

that gets a pocket in one side to receive a lock ( my guess)

The pocket's location and dimensions

are editable fields on the tab image.


Often in industry, there are arguments for and against

programming o the shop floor / on the machine.

This approach appears to allow  the operator

to modify the work, with guidance.


I hope we hear more about this.


TomP

?

On 10/23/24 7:31 PM, Kevin LaSanders wrote:
> Domi on the forum right? just do it in usercommand file. i have most of
> what you did already in a usercommand file, just edit the containers
> and stuff.
>
> https://forum.linuxcnc.org/media/kunena/attachments/25269/usercommand_dark_2022-03-20.py
>
> On Wed, Oct 23, 2024 at 5:10 PM Alec Ari via Emc-developers <
> emc...@li...> wrote:
>
>> Hey everyone,
>>
>> I haven't been following this thread too closely but I am curious... Can I
>> see a screenshot of the new proposed AXIS interface?
>>
>> Thanks!
>>
>> Alec
>>
>

Domi on the forum right? just do it in usercommand file. i have most of
what you did already in a usercommand file, just edit the containers
and stuff.

https://forum.linuxcnc.org/media/kunena/attachments/25269/usercommand_dark_2022-03-20.py

On Wed, Oct 23, 2024 at 5:10 PM Alec Ari via Emc-developers <
emc...@li...> wrote:

> Hey everyone,
>
> I haven't been following this thread too closely but I am curious... Can I
> see a screenshot of the new proposed AXIS interface?
>
> Thanks!
>
> Alec
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers
>

Hey everyone,

I haven't been following this thread too closely but I am curious... Can I see a screenshot of the new proposed AXIS interface?

Thanks!

Alec

Vom: Mon, 21 Oct 2024 14:57:11 +0100

> On Mon, 21 Oct 2024 at 13:26, Graham Inggs <gi...@de...> wrote:
> 
> > invalid escape sequence '\d'  
> 
> (many times)
> 
> As far as I am aware \d is a valid escape character in Python regex.
> These look like false-positives (given that as far as I know all the
> code mentioned is working.)
> 

Haven't looked into this special case but it looks like mixing python string escape sequences [1] with regex special characters/special sequences [2].


Then the solution would be to use raw strings:  r"(\d+)" instead of "(\d+)"


From the docs:

"Regular expressions use the backslash character ('\') to indicate special forms or to allow special characters to be used without invoking their special meaning. This collides with Python’s usage of the same character for the same purpose in string literals; for example, to match a literal backslash, one might have to write '\\\\' as the pattern string, because the regular expression must be \\, and each backslash must be expressed as \\ inside a regular Python string literal.

[...]

please note that any invalid escape sequences in Python’s usage of the backslash in string literals now generate a SyntaxWarning and in the future this will become a SyntaxError. This behaviour will happen even if it is a valid escape sequence for a regular expression.

[...]

The solution is to use Python’s raw string notation for regular expression patterns; backslashes are not handled in any special way in a string literal prefixed with 'r'. So r"\n" is a two-character string containing '\' and 'n', while "\n" is a one-character string containing a newline."



[1] https://docs.python.org/3/reference/lexical_analysis.html#escape-sequences
[2] https://docs.python.org/3/library/re.html#index-9

Best regards
-- 
Daniel

Hi Andy

On Mon, 21 Oct 2024 at 13:57, andy pugh <bod...@gm...> wrote:
> As far as I am aware \d is a valid escape character in Python regex.
> These look like false-positives (given that as far as I know all the
> code mentioned is working.)

This is a change in Python 3.12 [1].

"
A backslash-character pair that is not a valid escape sequence now
generates a SyntaxWarning, instead of DeprecationWarning. For example,
re.compile("\d+\.\d+") now emits a SyntaxWarning ("\d" is an invalid
escape sequence, use raw strings for regular expression:
re.compile(r"\d+\.\d+")).
"

Regards
Graham


[1] https://docs.python.org/3/whatsnew/3.12.html

On Mon, 21 Oct 2024 at 13:26, Graham Inggs <gi...@de...> wrote:

> invalid escape sequence '\d'

(many times)

As far as I am aware \d is a valid escape character in Python regex.
These look like false-positives (given that as far as I know all the
code mentioned is working.)

-- 
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Source: linuxcnc
Version: 2.9.3-1
User: deb...@li...
Usertags: syntaxwarning

Hi Maintainer

The SyntaxWarning below were emitted when this package was tested with
pipuarts[1].

Regards
Graham


[1] https://piuparts.debian.org/sid/source/l/linuxcnc.html


  Setting up linuxcnc-uspace (2.9.3-1+b2) ...
  /usr/lib/python3/dist-packages/linux_event.py:769: SyntaxWarning:
invalid escape sequence '\d'
    s = re.split("(\d+)", s)
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\T'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\T'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\C'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\C'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\P'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pncconf/data.py:319: SyntaxWarning:
invalid escape sequence '\M'
    self.qtplasmac_bnames =
["OHMIC\TEST","PROBE\TEST","SINGLE\CUT","NORMAL\CUT","TORCH\PULSE","FRAMING",
"USER\MANUAL", \
  /usr/lib/python3/dist-packages/pyngcgui.py:2207: SyntaxWarning:
invalid escape sequence '\('
    e_message = ".*Runtime message\(\): *(.*)"
  /usr/lib/python3/dist-packages/pyngcgui.py:2208: SyntaxWarning:
invalid escape sequence '\('
    e_warning = ".*Runtime warning\(\): *(.*)"
  /usr/lib/python3/dist-packages/pyngcgui.py:2209: SyntaxWarning:
invalid escape sequence '\('
    e_error   = ".*Runtime error\(\): *(.*)"
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:170:
SyntaxWarning: invalid escape sequence '\d'
    valid_size =
QtGui.QRegExpValidator(QRegExp('^((\d+(\.\d{,4})?)|(\.\d{,4}))$'))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:171:
SyntaxWarning: invalid escape sequence '\d'
    valid_radius =
QtGui.QRegExpValidator(QRegExp('^((\d{1,3}(\.\d{1,4})?)|(\.\d{1,4}))$'))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:174:
SyntaxWarning: invalid escape sequence '\d'
    valid_size =
QtGui.QRegExpValidator(QRegExp('^((\d+(\.\d{,3})?)|(\.\d{,3}))$'))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:175:
SyntaxWarning: invalid escape sequence '\d'
    valid_radius =
QtGui.QRegExpValidator(QRegExp('^((\d{1,4}(\.\d{1,3})?)|(\.\d{1,3}))$'))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:176:
SyntaxWarning: invalid escape sequence '\d'
    valid_feed = QtGui.QRegExpValidator(QRegExp('\d{0,5}[.]\d{0,1}'))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:178:
SyntaxWarning: invalid escape sequence '\d'
    self.lineEdit_spindle.setValidator(QtGui.QRegExpValidator(QRegExp('\d{0,5}')))
  /usr/lib/python3/dist-packages/qtvcp/lib/gcode_utility/hole_circle.py:181:
SyntaxWarning: invalid escape sequence '\d'
    self.lineEdit_first.setValidator(QtGui.QRegExpValidator(QRegExp('\d{0,3}[.]\d{0,2}')))
  /usr/lib/python3/dist-packages/qtvcp/lib/qt_ngcgui/ngcgui.py:154:
SyntaxWarning: invalid escape sequence '\d'
    valid = QtGui.QRegExpValidator(QRegExp('^[+-]?((\d+(\.\d{,4})?)|(\.\d{,4}))$'))
  /usr/lib/python3/dist-packages/qtvcp/lib/ripper/gcode_ripper.py:6109:
SyntaxWarning: invalid escape sequence '\['
    line = re.split( "([\[,\],\^,\*,\/,\%,\+,\-,\|  ,\&  ,\l ,\< ,\g
,\> ,\! ,\= ])", line)
  /usr/lib/python3/dist-packages/qtvcp/widgets/basic_probe.py:49:
SyntaxWarning: invalid escape sequence '\d'
    self.valid =
QtGui.QRegExpValidator(QRegExp('^[+-]?((\d+(\.\d{,4})?)|(\.\d{,4}))$'))
  /usr/lib/python3/dist-packages/qtvcp/widgets/basic_probe.py:51:
SyntaxWarning: invalid escape sequence '\d'
    self.valid =
QtGui.QRegExpValidator(QRegExp('^[+-]?((\d+(\.\d{,3})?)|(\.\d{,3}))$'))
  /usr/lib/python3/dist-packages/qtvcp/widgets/versa_probe.py:57:
SyntaxWarning: invalid escape sequence '\d'
    self.valid =
QtGui.QRegExpValidator(QtCore.QRegExp('^((\d{1,4}(\.\d{1,3})?)|(\.\d{1,3}))$'))
  /usr/lib/python3/dist-packages/qtvcp/widgets/versa_probe.py:59:
SyntaxWarning: invalid escape sequence '\d'
    self.valid =
QtGui.QRegExpValidator(QtCore.QRegExp('^((\d{1,3}(\.\d{1,4})?)|(\.\d{1,4}))$'))

[Petter Reinholdtsen]
> I drafted an adjusted attempt in
> <URL: https://github.com/LinuxCNC/linuxcnc/pull/3158 >.

The fix is now in 2.9 and master branches.

I hope it work on all architectures and platforms. :)

-- 
Happy hacking
Petter Reinholdtsen

thanks

Il giorno dom 20 ott 2024 alle ore 18:50 Petter Reinholdtsen
<pe...@hu...> ha scritto:
>
>
> I drafted an adjusted attempt in
> <URL: https://github.com/LinuxCNC/linuxcnc/pull/3158 >.
>
> --
> Happy hacking
> Petter Reinholdtsen
>
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

I drafted an adjusted attempt in
<URL: https://github.com/LinuxCNC/linuxcnc/pull/3158 >.

-- 
Happy hacking
Petter Reinholdtsen

Hi,

Am Samstag, dem 19.10.2024 um 13:03 +0000 schrieb Steffen Möller via
Emc-developers:
> Hello,
> 
> somewhen during the translations I the posemaths routine popped up
> IIRC and I had wondered about the passing by value of those doubles.
> For 64bit machines this likely does not make too much of a
> difference, and the compilers are not stupid either, but for 32bit
> machines and without link-time optimisation, I guess it helps when
> the value does not need to be copied.
> 
[...]
> Comments?

Is this really worth doing? I don't think it will make any measureable
difference -- I would not bother. That stuff probably is not even used.

In the long run, the schism between the C-structs and the C++ parallel-
implementation has to go IMHO. Those methods could be moved to the
header file and marked constexpr/consteval. I think it should be
possible to inherit from the C-structs and in the C++ code just
downcast. 

Also it seems codesize increases with const reference:
https://godbolt.org/z/MzTPb9jx5 vs. https://godbolt.org/z/xzrneEYdT

best regards
Robert

Hello,

somewhen during the translations I the posemaths routine popped up IIRC and I had wondered about the passing by value of those doubles. For 64bit machines this likely does not make too much of a difference, and the compilers are not stupid either, but for 32bit machines and without link-time optimisation, I guess it helps when the value does not need to be copied.

My routines have this already, especially for the non-scalar values, like
src//libnml/posemath/posemath.cc:// PM_POSE class
src//libnml/posemath/posemath.cc:PM_POSE inv(const PM_POSE &p)
src//libnml/posemath/posemath.cc:    PM_POSE ret;
src//libnml/posemath/posemath.cc:PM_POSE operator +(const PM_POSE &p)
src//libnml/posemath/posemath.cc:PM_POSE operator -(const PM_POSE &p)
src//libnml/posemath/posemath.cc:    PM_POSE ret;
src//libnml/posemath/posemath.cc:int operator ==(const PM_POSE &p1, const PM_POSE &p2)
src//libnml/posemath/posemath.cc:int operator !=(const PM_POSE &p1, const PM_POSE &p2)
src//libnml/posemath/posemath.cc:PM_POSE operator *(const PM_POSE &p1, const PM_POSE &p2)
src//libnml/posemath/posemath.cc:PM_POSE::PM_POSE(PM_CCONST PM_POSE & p)
src//libnml/posemath/posemath.cc:PM_HOMOGENEOUS::PM_HOMOGENEOUS(PM_CONST PM_POSE PM_REF p)

but others very much not so, like

src//libnml/posemath/posemath.cc:PM_POSE::PM_POSE(PM_CARTESIAN v, PM_QUATERNION q)
src//libnml/posemath/posemath.cc:PM_POSE::PM_POSE(double x, double y, double z,
src//libnml/posemath/posemath.cc:int PM_LINE::init(PM_POSE start, PM_POSE end)
src//libnml/posemath/posemath.cc:int PM_LINE::point(double len, PM_POSE * point)
src//libnml/posemath/posemath.cc:int PM_CIRCLE::init(PM_POSE start, PM_POSE end,
src//libnml/posemath/posemath.cc:int PM_CIRCLE::point(double angle, PM_POSE * point)

so I suggest I look at them all and transform

PM_CARTESIAN::PM_CARTESIAN(double _x, double _y, double _z)
{
    x = _x;
    y = _y;
    z = _z;
}

to

PM_CARTESIAN::PM_CARTESIAN(const double& _x, const double& _y, const double& _z)
{
    x = _x;
    y = _y;
    z = _z;
}

and for

PM_ROTATION_MATRIX::PM_ROTATION_MATRIX(double xx, double xy, double xz,
    double yx, double yy, double yz, double zx, double zy, double zz)

well - the number of circles saved sum up :)

Would this be considered worthwhile to be addressed?

Now, even though it is just an introduction of "const" and "&", and we have our peer review, there is a chance I mess something up with these low-level routines. I should hence also come up with some tests, right? And better I have the tests prior to change.

Comments?

Best,
Steffen

Oops, false alarm, I was incorrectly logged in to GitHub.



> On 19 Oct 2024, at 11:50 AM, Phill Carter via Emc-developers <emc...@li...> wrote:
> 
> I attempted to create a PR this morning and received this:
> 
> <Screenshot 2024-10-19 at 11.46.17 AM.png>
> 
> I was under the impression that anyone with a GitHub account could create a PR.
> 
> Have I done something wrong?
> 
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers

I attempted to create a PR this morning and received this:

FYI: The status of the mesaflash source package
in Debian's testing distribution has changed.

  Previous version: 3.4.6-1
  Current version:  3.4.6-1.1

-- 
This email is automatically generated once a day.  As the installation of
new packages into testing happens multiple times a day you will receive
later changes on the next day.
See https://release.debian.org/testing-watch/ for more information.

not understand why but these evening (in italy) connection is slow,
discontinue and unstable ..... maybe local problem ... but seems other
....

regards

Hi andy (2024.10.16_18:36:34_+0000)

> On Wed, 9 Oct 2024 at 17:23, <ste...@de...> wrote:
> 
> > python3 -c 'import sysconfig; print(sysconfig.get_path("platlib", "deb_system"))'
> 
> I tried this, it prompted this bug report from an OpenSUSE user.
> https://github.com/Eckeneckepen/linuxcnc/commit/fa2bfe0cd4eecd1d06d9ca548e4cb852aad67053#commitcomment-148017436

Sorry, that was an example meant to demonstrate a point, not an upstream
friendly patch (as I described in the next paragraph).

Only debian systems have the deb_system scheme.

Stefano

-- 
Stefano Rivera
  http://tumbleweed.org.za/
  +1 415 683 3272

On Wed, 9 Oct 2024 at 17:23, <ste...@de...> wrote:

> python3 -c 'import sysconfig; print(sysconfig.get_path("platlib", "deb_system"))'

I tried this, it prompted this bug report from an OpenSUSE user.
https://github.com/Eckeneckepen/linuxcnc/commit/fa2bfe0cd4eecd1d06d9ca548e4cb852aad67053#commitcomment-148017436

> An upstream friendly patch would be to interrogate the build system's
> prefix, and if it is going to be installed into "/usr", select the
> "deb_system" scheme, if available, otherwise use the default scheme.

Frankly, at this point, I am tempted to just hard-code it.



--
atp
"A motorcycle is a bicycle with a pandemonium attachment and is
designed for the especial use of mechanical geniuses, daredevils and
lunatics."
— George Fitch, Atlanta Constitution Newspaper, 1912

Your message dated Sat, 12 Oct 2024 15:00:20 +0000
with message-id <E1s...@fa...>
and subject line Bug#1074041: fixed in mesaflash 3.4.6-1.1
has caused the Debian Bug report #1074041,
regarding mesaflash: FTBFS: Add support for loongarch64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bu...
immediately.)


-- 
1074041: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1074041
Debian Bug Tracking System
Contact ow...@bu... with problems

Thank you for your contribution to Debian.



Accepted:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Fri, 27 Sep 2024 15:48:44 +0200
Source: mesaflash
Built-For-Profiles: noudeb
Architecture: source
Version: 3.4.6-1.1
Distribution: unstable
Urgency: medium
Maintainer: LinuxCNC Developers <emc...@li...>
Changed-By: Gianfranco Costamagna <loc...@de...>
Closes: 1074041
Changes:
 mesaflash (3.4.6-1.1) unstable; urgency=medium
 .
   * Non-maintainer upload.
   [ zhangdandan <zha...@lo...> ]
   * Add support for loongarch64 (Closes: #1074041)
Checksums-Sha1:
 5f2c7cdcb5470f4c5154c9beecefa5918e9e6be4 1982 mesaflash_3.4.6-1.1.dsc
 e05a4f4b7a3d249ea197e412f0d41c1d997368d2 4216 mesaflash_3.4.6-1.1.debian.tar.xz
 b0de86946826ada96c18bee7fc6102949ff96540 8097 mesaflash_3.4.6-1.1_source.buildinfo
Checksums-Sha256:
 5fff2a1ac395a1ae3beefeefceb81905dd3398d01fa14803dad4aa9ab5de3853 1982 mesaflash_3.4.6-1.1.dsc
 057e0298b5dc5930f0078592a8d49e44784a8f83c7c4049db174fb65884ab36f 4216 mesaflash_3.4.6-1.1.debian.tar.xz
 fcfc9df087879b97247a242d75c79d2c46d6cf81a37e77c84138414876ce640c 8097 mesaflash_3.4.6-1.1_source.buildinfo
Files:
 7c8c9898ebb4bdc7432dbccf09dee111 1982 misc optional mesaflash_3.4.6-1.1.dsc
 c6da4c7299f66d239459fb962665925e 4216 misc optional mesaflash_3.4.6-1.1.debian.tar.xz
 56d756b3804229a7eb8fd0751f1d365b 8097 misc optional mesaflash_3.4.6-1.1_source.buildinfo

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEkpeKbhleSSGCX3/w808JdE6fXdkFAmb2uAUACgkQ808JdE6f
XdmhHhAAy5dQ98yIJIBRihTAN0DjJuWnNRsS+PDH3OXWt+PkJFrt0U4T36E8atos
qR3dEfVlVc4GPockl/HCExDrN/QXaipI2AuTHxykogA5GCtawxOovZQQ77yBfBqT
UBu0P3LYRmbqADcINN/0JTvtVVNYqzmnLzy8FkkPsGPqfkqAyswuW0icHpTXAeRc
E7NVT7pcphHiEVyfZZ1WsZMvaHNaLnR/xUTfLxpFORyIL9h66GoUaVlRN8epe8o3
DDr/0khu/VZu7avT29hUY8CItUlBDz70zPu1G1DxLoc413AC35ho8YgehHco6/Cp
xurz5f/kZsuY9SDsayI0QNNXyMcr5LflZkpEeeRawdyT+QV1+A44Lmqsa9bdevbR
rA/rIiQPUtwE6LFbaS3Uev22+YSQzccwyE86V/CH+ad9RBae/68xcsn+LoE2rm/m
mCpipPGtQcvE19uMpwcGfy+rGqngSpYLhBRSMHTvgZasrDLZcg0eAgea3jQXOXlU
N+ETtcEG7Z7X4zY1rPd8QoFvSnBXsXwQ9/ryU6T2JLJQSsBDy94eB3zkrzC08v9S
3ysACrzBrBEgUrPQqH8PnVGPdpMuO24XEN8Bwg67INsz8jnWUTPIhl/b8OZl+uRR
wxYCvCRI3jD452FQJfDltEUgHJ0Njcikyyb2TqlgxY3HqzF8LXc=
=ew0s
-----END PGP SIGNATURE-----

You could try install the dependencies following the instructions from 
the section "Building LinuxCNC".
I did that and built LinuxCNC on Ubuntu 24 and it was straight forward 
without problems. I only had to install two additional runtime-packages.

Am 12.10.24 um 11:16 schrieb theman whosoldtheworld:
> sorry at all ... i'm not developper but a bad user, so for 3 day try
> and try again to install over ubuntu 24 (I know the "devil" ... )
> and linux mint 22 ... so I see these problem .... 2.9.3 have it ...
> but seems 2.10 is not affect, install on plain SO for 6 time on 2
> different machine I3 11th and N95 .... so think what work for 2.10,
> can work for all ... not check what difference is done in particular
> from 2.9.3 and 2.10.0 .... but it work great. So thanks to Andy again
> and again ...
>
> Il giorno mer 9 ott 2024 alle ore 18:23 <ste...@de...> ha scritto:
>> Hi Petter (2024.10.09_07:45:10_+0000)
>>> Unfortunately, the change in src/configure.ac, where
>>>
>>>    python3 -c 'import distutils.sysconfig; print(distutils.sysconfig.get_python_lib())'
>>>
>>> was replaced with
>>>
>>>    python3 -c 'import sysconfig; print(sysconfig.get_path("platlib"))'
>>>
>>> changes the used path from /usr/lib/python3/dist-packages to
>>> /usr/local/lib/python3.11/dist-packages, which put the python library
>>> files in the wrong location.
>> That should actually be OK, dh_python3 will move those to the right
>> place.
>>
>>> I am not sure what a good solution is for this, but just wanted to
>>> document the problem.
>> You could export DEB_PYTHON_INSTALL_LAYOUT=deb which would change the
>> behaviour of that.
>>
>> Or patch it to say:
>>
>> python3 -c 'import sysconfig; print(sysconfig.get_path("platlib", "deb_system"))'
>>
>> An upstream friendly patch would be to interrogate the build system's
>> prefix, and if it is going to be installed into "/usr", select the
>> "deb_system" scheme, if available, otherwise use the default scheme.
>>
>> Stefano
>>
>> --
>> Stefano Rivera
>>    http://tumbleweed.org.za/
>>    +1 415 683 3272
>>
>>
>> _______________________________________________
>> Emc-developers mailing list
>> Emc...@li...
>> https://lists.sourceforge.net/lists/listinfo/emc-developers
>
> _______________________________________________
> Emc-developers mailing list
> Emc...@li...
> https://lists.sourceforge.net/lists/listinfo/emc-developers