Mailinglist Archive: opensuse-packaging (118 mails)
< Previous | Next > |
Re: [opensuse-packaging] problem with python package
- From: Klaas Freitag <freitag@xxxxxxxxxxxx>
- Date: Tue, 16 Jun 2015 13:11:14 +0200
- Message-id: <55800452.2020203@opensuse.org>
On 16.06.2015 12:56, Howard Guo wrote:
Howard,
Thanks for the reply! Before the package was indeed noarch, which I
removed for this build. Now I assume it builds the arch that is
specified in osc build call. That is 64 bit, but still the
%python-sitelib macro points to /usr/lib/... rather than /usr/lib64/...
However, %python_sitearch points to the /usr/lib64/...
Short: I am not sure if that is the problem.
thanks,
Klaas
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
Howard,
Please double check the package's architecture. When there is C code in
a Python package, building on incorrect architecture will produce errors
like those you encountered.
Thanks for the reply! Before the package was indeed noarch, which I
removed for this build. Now I assume it builds the arch that is
specified in osc build call. That is 64 bit, but still the
%python-sitelib macro points to /usr/lib/... rather than /usr/lib64/...
However, %python_sitearch points to the /usr/lib64/...
Short: I am not sure if that is the problem.
thanks,
Klaas
On 16/06/15 12:52, Klaas Freitag wrote:
Hi,
I am trying to update devel:languages:python python-netlib to the new
version. It's a dependency of mitmproxy that I also wanna update.
The new version has some C code embedded with cffi which I haven't seen
before.
My local build results in http://paste.opensuse.org/25035334 after I
added a couple of dependencies. It builds, but has the install errors.
Can anybody explain what the problem is? How can that be fixed? How do I
handle the debug files? Where should the compiled shared library go?
Thanks,
Klaas
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx
< Previous | Next > |