Package Details: python-sabyenc3 4.0.2-1

Git Clone URL: https://aur.archlinux.org/python-sabyenc3.git (read-only, click to copy)
Package Base: python-sabyenc3
Description: yEnc package optimized for use within SABnzbd.
Upstream URL: https://github.com/sabnzbd/sabyenc
Licenses: LGPLv3
Submitter: fryfrog
Maintainer: fryfrog
Last Packager: fryfrog
Votes: 1
Popularity: 0.38
First Submitted: 2020-04-20 16:56
Last Updated: 2020-06-17 03:28

Latest Comments

fryfrog commented on 2020-08-14 19:23

Humans are the worst, eh? :)

courtnek commented on 2020-08-14 19:04

Hah, because I'm dumb and building the packages on an account that has a python symlink in its path ahead of the system to force python2 from years back in 2016 to work around some other build issue. Removing the symlink lets me build the package as normal. Thanks for the help!

fryfrog commented on 2020-08-14 19:02

Oh sheesh, yeah look at that. Why is it trying to build against python2? :|

courtnek commented on 2020-08-14 18:55

Thats a good point. It looks like my temp directories reference python2.7 and yours are 3.8. I've been using the sabnzbd aur packages for years and years (thanks for your contributions there btw), and so I assume this is a part of the python 3 move.

fryfrog commented on 2020-08-14 18:08

gcc -pthread -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -fno-semantic-interposition -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -march=x86-64 -mtune=generic -O3 -pipe -fno-plt -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python3.8 -c src/sabyenc3.c -o build/temp.linux-x86_64-3.8/src/sabyenc3.o

gcc -pthread -shared -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -fno-semantic-interposition -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -Wl,-O1,--sort-common,--as-needed,-z,relro,-z,now -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -D_FORTIFY_SOURCE=2 build/temp.linux-x86_64-3.8/src/sabyenc3.o -L/usr/lib -o build/lib.linux-x86_64-3.8/sabyenc3.cpython-38-x86_64-linux-gnu.so

^ My gcc lines are pretty different from yours, but I don't have any bright ideas of why. I don't think I've done anything on my system to change how compiles are done. Have you tuned yours?

courtnek commented on 2020-08-14 17:58

I'm getting the following error on my system:

running install
running build
running build_ext
building 'sabyenc3' extension
creating build
creating build/temp.linux-x86_64-2.7
creating build/temp.linux-x86_64-2.7/src
gcc -pthread -fno-strict-aliasing -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -DNDEBUG -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -march=x86-64 -mtune=generic -O2 -pipe -fno-plt -D_FORTIFY_SOURCE=2 -fPIC -I/usr/include/python2.7 -c src/sabyenc3.c -o build/temp.linux-x86_64-2.7/src/sabyenc3.o
src/sabyenc3.c:105:15: error: variable ‘sabyenc3_definition’ has initializer but incomplete type
  105 | static struct PyModuleDef sabyenc3_definition = {
      |               ^~~~~~~~~~~
src/sabyenc3.c:106:5: error: ‘PyModuleDef_HEAD_INIT’ undeclared here (not in a function)
  106 |     PyModuleDef_HEAD_INIT,
      |     ^~~~~~~~~~~~~~~~~~~~~
src/sabyenc3.c:106:5: warning: excess elements in struct initializer
src/sabyenc3.c:106:5: note: (near initialization for ‘sabyenc3_definition’)
src/sabyenc3.c:107:5: warning: excess elements in struct initializer
  107 |     "sabyenc3",
      |     ^~~~~~~~~~
src/sabyenc3.c:107:5: note: (near initialization for ‘sabyenc3_definition’)
src/sabyenc3.c:108:5: warning: excess elements in struct initializer
  108 |     "Processing of raw NNTP-yEnc streams for SABnzbd.",
      |     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/sabyenc3.c:108:5: note: (near initialization for ‘sabyenc3_definition’)
src/sabyenc3.c:109:5: warning: excess elements in struct initializer
  109 |     -1,
      |     ^
src/sabyenc3.c:109:5: note: (near initialization for ‘sabyenc3_definition’)
src/sabyenc3.c:110:5: warning: excess elements in struct initializer
  110 |     sabyenc3_methods
      |     ^~~~~~~~~~~~~~~~
src/sabyenc3.c:110:5: note: (near initialization for ‘sabyenc3_definition’)
src/sabyenc3.c: In function ‘PyInit_sabyenc3’:
src/sabyenc3.c:116:24: warning: implicit declaration of function ‘PyModule_Create’; did you mean ‘PyModule_Check’? [-Wimplicit-function-declaration]
  116 |     PyObject* module = PyModule_Create(&sabyenc3_definition);
      |                        ^~~~~~~~~~~~~~~
      |                        PyModule_Check
src/sabyenc3.c:116:24: warning: initialization of ‘PyObject *’ {aka ‘struct _object *’} from ‘int’ makes pointer from integer without a cast [-Wint-conversion]
src/sabyenc3.c:118:12: warning: ‘return’ with a value, in function returning void
  118 |     return module;
      |            ^~~~~~
src/sabyenc3.c:113:16: note: declared here
  113 | PyMODINIT_FUNC PyInit_sabyenc3(void) {
      |                ^~~~~~~~~~~~~~~
src/sabyenc3.c: At top level:
src/sabyenc3.c:105:27: error: storage size of ‘sabyenc3_definition’ isn’t known
  105 | static struct PyModuleDef sabyenc3_definition = {
      |                           ^~~~~~~~~~~~~~~~~~~
error: command 'gcc' failed with exit status 1
==> ERROR: A failure occurred in package().
    Aborting...
error making: %!s(func() string=0x564f51439bb0)

Any clues as to what might be misconfigured? The package seems to install fine via pip

yochananmarqos commented on 2020-05-06 20:11

The description does not match the package.