Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-20 Thread Nico Schlömer
Actually, you usually don't get these kind of warnings for Python extension modules. The warning is emitted only if a module has SONAME, and it typically doesn't. You might want to get rid of SONAMEs That indeed was the problem. Thanks! It's a CMake/SWIG build, and I now added a patch to set

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-18 Thread Mathieu Malaterre
On Tue, Mar 18, 2014 at 12:05 AM, Nico Schlömer nico.schloe...@gmail.com wrote: Understood, thanks! I'll just ignore the warnings of the type ``` dpkg-shlibdeps: warning: debian/python-pytrilinos/usr/lib/python2.7/dist-packages/PyTrilinos/NOX/_Abstract.so contains an unresolvable reference

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-18 Thread Jakub Wilk
* Russ Allbery r...@debian.org, 2014-03-17, 19:12: Understood, thanks! I'll just ignore the warnings of the type ``` dpkg-shlibdeps: warning: debian/python-pytrilinos/usr/lib/python2.7/dist-packages/PyTrilinos/NOX/_Abstract.so contains an unresolvable reference to symbol PyString_FromFormat:

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-18 Thread Russ Allbery
Jakub Wilk jw...@debian.org writes: Actually, you usually don't get these kind of warnings for Python extension modules. The warning is emitted only if a module has SONAME, and it typically doesn't. If you build a module with libtool's -module flag, it looks like it still gets an SONAME. I'm

public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-17 Thread Nico Schlömer
Hi all, I'm building a package with Python support and would like to reduce the number of warnings that dh_python2 gives me. One of them is public extension linked with libpython2.7 for a number of libraries. It is true that libpython2.7 is linked into them, $ readelf -d /path/to/_ML.so

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-17 Thread Mathieu Malaterre
On Mon, Mar 17, 2014 at 3:49 PM, Nico Schlömer nico.schloe...@gmail.com wrote: $ readelf -d /path/to/_ML.so [...] 0x0001 (NEEDED) Shared library: [libpython2.7.so.1.0] [...] but when I don't, builds with -Wl,-no-undefined will fail. Well then do not use

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-17 Thread Jakub Wilk
* Nico Schlömer nico.schloe...@gmail.com, 2014-03-17, 15:49: I'm building a package with Python support and would like to reduce the number of warnings that dh_python2 gives me. One of them is public extension linked with libpython2.7 for a number of libraries. It is true that libpython2.7

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-17 Thread Nico Schlömer
Understood, thanks! I'll just ignore the warnings of the type ``` dpkg-shlibdeps: warning: debian/python-pytrilinos/usr/lib/python2.7/dist-packages/PyTrilinos/NOX/_Abstract.so contains an unresolvable reference to symbol PyString_FromFormat: it's probably a plugin. ``` then. Cheers, Nico On

Re: public extension linked with libpython* vs. -Wl,-no-undefined

2014-03-17 Thread Russ Allbery
Nico Schlömer nico.schloe...@gmail.com writes: Understood, thanks! I'll just ignore the warnings of the type ``` dpkg-shlibdeps: warning: debian/python-pytrilinos/usr/lib/python2.7/dist-packages/PyTrilinos/NOX/_Abstract.so contains an unresolvable reference to symbol PyString_FromFormat: