In my python application, I need to include a .so binary I built of a custom gstreamer plugin. My python application works fine with this plugin when launching from the command line.
Now that I am packaging my python application into a fedora rpm, I need to compile the plugin as part of the packaging process?
I ask because when I try to include the .so file in %files and part of the manifest, I get this error from rpmbuild:
"arch dependent binaries in noarch package"
Could someone point me to an example of how to create a spec file which shows how to include "nested" c code so as to avoid this error and successfully build my rpm?
Thanks much. Erik
Just remove the line 'BuildArch: noarch' from your specfile?
On Wed, Jan 26, 2011 at 9:59 PM, Erik Blankinship jedierikb@gmail.comwrote:
In my python application, I need to include a .so binary I built of a custom gstreamer plugin. My python application works fine with this plugin when launching from the command line.
Now that I am packaging my python application into a fedora rpm, I need to compile the plugin as part of the packaging process?
I ask because when I try to include the .so file in %files and part of the manifest, I get this error from rpmbuild:
"arch dependent binaries in noarch package"
Could someone point me to an example of how to create a spec file which shows how to include "nested" c code so as to avoid this error and successfully build my rpm?
Thanks much. Erik
python-devel mailing list python-devel@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/python-devel
On Wed, Jan 26, 2011 at 10:15 AM, Robin Lee robinlee.sysu@gmail.com wrote:
Just remove the line 'BuildArch: noarch' from your specfile?
That was easy! Thank you.
Now, if I wanted to build a noarch rpm, is there an example of how I would go about building my custom gstreamer .so plugin files in my spec file? Or am I not understanding how "noarch" works?
On Wed, 2011-01-26 at 20:48 -0500, Erik Blankinship wrote:
On Wed, Jan 26, 2011 at 10:15 AM, Robin Lee robinlee.sysu@gmail.com wrote: Just remove the line 'BuildArch: noarch' from your specfile?
That was easy! Thank you.
Now, if I wanted to build a noarch rpm, is there an example of how I would go about building my custom gstreamer .so plugin files in my spec file? Or am I not understanding how "noarch" works?
Right. The 'noarch' tag denotes a 'binary' package that is not arch-specific; it will work without modification on any architecture. A package that includes compiled C code is clearly *not* arch-independent, you can't apply the noarch tag to it. If your package includes a compiled C extension, you cannot mark it as noarch.
I suspect you may want to read the Python packaging guidelines - http://fedoraproject.org/wiki/Packaging:Python - to make sure you're doing everything else right, too. Pay particular attention to python_sitelib vs. python_sitearch .
python-devel@lists.fedoraproject.org