Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#39429 - [python-sfml] "import sfml" results in ImportError undefined symbol Vector2
Attached to Project:
Community Packages
Opened by David Vadovszki (mindkeep) - Saturday, 15 March 2014, 02:29 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 15 March 2014, 09:17 GMT
Opened by David Vadovszki (mindkeep) - Saturday, 15 March 2014, 02:29 GMT
Last edited by Sven-Hendrik Haase (Svenstaro) - Saturday, 15 March 2014, 09:17 GMT
|
DetailsDescription:
The current version of the package hits an undefined symbol / Import Error. I downloaded the PKGBUILD file, and after manually rebuilding and installing the package (without modification), the ImportError goes away, and things appear to work as intended (though this is the first time I've used the module). So perhaps this is a just a "out of date" problem, but because the we're still on v1.3, that's technically not the case. Additional info: * package version(s) 1.3-2 * config and/or log files etc. n/a (see below) Steps to reproduce: $ python Python 3.3.4 (default, Feb 11 2014, 15:56:08) [GCC 4.8.2 20140206 (prerelease)] on linux Type "help", "copyright", "credits" or "license" for more information. >>> import sfml Traceback (most recent call last): File "<stdin>", line 1, in <module> File "/usr/lib/python3.3/site-packages/sfml/__init__.py", line 12, in <module> from sfml.window import * ImportError: /usr/lib/python3.3/site-packages/sfml/window.cpython-33m.so: undefined symbol: _ZN2sf6Window7setSizeENS_7Vector2IjEE >>> Workaround: As mentioned above, manually rebuilding the package seems to fix the problem. |
This task depends upon
Closed by Sven-Hendrik Haase (Svenstaro)
Saturday, 15 March 2014, 09:17 GMT
Reason for closing: Fixed
Saturday, 15 March 2014, 09:17 GMT
Reason for closing: Fixed