On Fri, Jan 11, 2013 at 07:08:19PM +0100, Johannes Weberhofer wrote:
Am 10.01.13 18:42, schrieb Cristian Rodríguez:
El 11/01/13 14:11, Matwey V. Kornilov escribió:
Cristian Rodr?guez wrote:
No, what you have to do is remove "BuildArch: noarch" from the spec file.
The package contains arch-specific binaries.
To which architecture it must be assigned?
To none, you have to let rpm decide that.
The package contains binaries for
multiple architectures not coinciding with host arch.
Then it is broken, the binaries must be built for target the package is being created.
The package is a noarch package; the .so files are used on the penetrated system; when I understand documentation currect, all .so files must be available after instalation because sqlmap decides during the analysis process which library to inject on the target server.
Hi Johannes, this is a big missunderstanding. If package installs architecture dependent files (assuming all .so files are shared objects, and not something else), then it it not noarch package. As far I can see, all you did is that you have unpacked the binaries from a tarball, which is not how packages are normally done. The normal approach is build everything from source - if nothing it gives you an ability to change things (like where so files will be installed and from where will be loaded). So the reasonable approach is to 1.) remove all .so files from a tarball 2.) build them in %build phase - this implies BuildArch: noarch removal 3.) install them to %{_libdir}/... 4.) change the code to look for them in a %{_libdir} Regards Michal Vyskocil