search

binarycrusader / libproxy

Automatically exported from code.google.com/p/libproxy
GNU Lesser General Public License v2.1
0 stars 0 forks source link

always test for the right python noarch module path #149

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1 build libproxy 0.4.6 on python x86_64 where arch dependant data are in 
/usr/lib64
2. the arch independant libproxy python binding pick the arch dependant module 
path, which is wrong.

What is the expected output? What do you see instead?
Cmake script should discover the accurate arch independant path automatically 
and rely on that.

What version of the product are you using? On what operating system?
Fedora 13/14/15 x86_64

Please provide any additional information below.
In fedora that's also break the noarch submodule path where noarch RPM sub 
package can be built from x86_64 or x86_32 independantly.

Original issue reported on code.google.com by kwiz...@gmail.com on 7 Nov 2010 at 6:11

Attachments:

GoogleCodeExporter commented 9 years ago 
Small variation of this committed as r796.

Original comment by dominiqu...@gmail.com on 8 Apr 2011 at 2:43