On 8/29/22 15:12, Peter J. Holzer wrote:
On 2022-08-29 13:43:18 -0400, gene heskett wrote:
On 8/29/22 12:50, Mark Bourne wrote:
Roel Schroeven wrote:
$ pip3 install -r requirements.txt  # finally invoke pip3

or:

$ {path_to_venv}/bin/pip3 install -r requirements.txt
That got me to showstopper #2: (lengthy warniing)

[...]
       checking for dbus-1 >= 1.8... no
       configure: error: Package requirements (dbus-1 >= 1.8) were not met:

       No package 'dbus-1' found
Since this message comes from configure, it is probably looking
for the development version of the dbus library here.

     apt search dbus-1

reveals (among other things):

     libdbus-1-dev/jammy 1.12.20-2ubuntu4 amd64
       simple interprocess messaging system (development headers)

(this is on Ubuntu, so the version number is probably different, but the
package name should be the same as on Debian.)

So you invoke

     apt install libdbus-1-dev

and try again. At which point you will probably discove another missing
library. Rinse and repeat.
You left out the wash, ;) The next missing dev was a gtk thingy, but search only returned one .dev. One for spice-gtk, and that pulled in around 100 more packages, and now its stuck on wxPython for about 35 minutes and, way into swap, like several hundred megs & growing. I even went to its keyboard and shut down chromium to give it more play room. Didn't seem to help though. But it hasn't errored, and swap is going  down a meg here and there. Pounding that poor, cheap sd card all to hell I expect. At some point, I'll unpack a startech usb3-sata cable and try an SSD. But I'll not disturb this just yet.

Works well on an r-pi4b where I can build linuxcnc in half an hour from the git pull. I run a 3/4 ton, 80 yo Sheldon lathe with linuxcnc just to see if I could do it, first on an rpi3b. Had to build my own realtime kernel and figure out how to install it because I wanted to do it on a pi, got black holed on their forum. The amazing part is that the tarball to install
it is only 28 megs uncompressed.
Ideally the README should mention such dependencies, but since the exact
names of the packages depend on the distribution, it will often be vague
unless you happen to use the same distribution as the developer.
Your forgot to mention that each packager is working in his own sound proof booth, so each comes up with a somewhat different way to pound that square peg into a 7 point hole.
;o)>

It was obviously going to take hours so I took a nap and 4 hours later it had left out a few things but kept on going until it hit another showstopper while building wxPython-4.1.
At which point it spit out 2600 some lines of backtrace.

Ending with this:
     In file included from ../../../../sip/cpp/sip_glcanvaswxGLContext.cpp:10:       ../../../../sip/cpp/sipAPI_glcanvas.h:865:198: error: ‘wxGLCanvasName’ was not declared in this scope; did you mean ‘wxGLCanvas’?         865 |     wxGLCanvas(wxWindow *parent, const wxGLAttributes &dispAttrs, wxWindowID id=wxID_ANY, const wxPoint &pos=wxDefaultPosition, const wxSize &size=wxDefaultSize, long style=0, const wxString &name=wxGLCanvasName, const wxPalette &palette=wxNullPalette)
| ^~~~~~~~~~~~~~
| wxGLCanvas

      Waf: Leaving directory `/tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/build/waf/3.1/gtk3'
      Build failed
       -> task in '_glcanvas' failed with exit status 1 (run with -v to display more information)        -> task in '_glcanvas' failed with exit status 1 (run with -v to display more information)        -> task in '_glcanvas' failed with exit status 1 (run with -v to display more information)        -> task in '_glcanvas' failed with exit status 1 (run with -v to display more information)       Command '"/home/gene/printrun/Printrun/venv/bin/python3" /tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/bin/waf-2.0.19 --wx_config=/tmp/pip-install-1myz6noi/wxpython_5fdcad39f0c544599dd49fdd522391f2/build/wxbld/gtk3/wx-config --gtk3 --python="/home/gene/printrun/Printrun/venv/bin/python3" --out=build/waf/3.1/gtk3 configure build ' failed with exit code 1.
      Finished command: build_py (100m40.712s)
      Finished command: build (171m37.482s)
      Command '"/home/gene/printrun/Printrun/venv/bin/python3" -u build.py build' failed with exit code 1.
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> wxPython

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
================
Now, I have the unpacked tarball of wxPython-4.2.0 sitting in /home/gene/src.

Where would I mv it to to substituted for the 4.1 since 4.1 isn't quite ready for prime time?

I changed the 1 to a 2 in requirements.txt, but that exited in a few seconds after it downloaded another copy of the tarball, with another error I have see before while
trying to build it in /home/gene/src's/unpacked_tarball tree.

paste of error:

(venv) gene@rock64:~/printrun/Printrun$ ./venv/bin/pip3 install -r requirements.txt Ignoring pyobjc-framework-Cocoa: markers 'sys_platform == "darwin"' don't match your environment Ignoring pyreadline: markers 'sys_platform == "win32"' don't match your environment Requirement already satisfied: pyserial>=3.0 in ./venv/lib/python3.10/site-packages (from -r requirements.txt (line 1)) (3.5)
Collecting wxPython==4.2.0
  Using cached wxPython-4.2.0.tar.gz (71.0 MB)
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [8 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "/tmp/pip-install-x9vpdn0f/wxpython_75085d87ddc7455cb159bbbb95177417/setup.py", line 27, in <module>           from buildtools.config import Config, msg, opj, runcmd, canGetSOName, getSOName         File "/tmp/pip-install-x9vpdn0f/wxpython_75085d87ddc7455cb159bbbb95177417/buildtools/config.py", line 30, in <module>
          from attrdict import AttrDict
      ModuleNotFoundError: No module named 'attrdict'
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: metadata-generation-failed

× Encountered error while generating package metadata.
╰─> See above for output.

note: This is an issue with the package mentioned above, not pip.
hint: See above for details.
(venv) gene@rock64:~/printrun/Printrun$

I've found it , the src tarball.gz. In /home/gene/Downloads.

Is that tarball updatable? Or should I ignore it & go back to wxPython-4.1?
Is it fixable?
         hp

Thanks Peter. Take care and stay well.

Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
 - Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>

--
https://mail.python.org/mailman/listinfo/python-list

Reply via email to