From luisgpm at linux.vnet.ibm.com Thu Dec 2 01:38:59 2010 From: luisgpm at linux.vnet.ibm.com (Luis Machado) Date: Wed, 01 Dec 2010 22:38:59 -0200 Subject: [Patches] [PATCH] Use lib/lib64 based on the libdir configure variable Message-ID: <1291250339.3774.11.camel@gargoyle> Hi, Python's build system (at least for 2.6.6) is not 32/64-bit aware in the sense that it always uses "lib" as the default lib/modules/config path. This patch handles this "problem" through the libdir configure variable. For example: --libdir=\${prefix}/lib64 --libdir=\${prefix}/lib This also changes the builtin paths that Python uses to look for lib/modules depending on what's set in the build. -------------- next part -------------- A non-text attachment was scrubbed... Name: py_libpath_fix.diff Type: text/x-patch Size: 10271 bytes Desc: not available URL: From luisgpm at linux.vnet.ibm.com Thu Dec 2 01:29:43 2010 From: luisgpm at linux.vnet.ibm.com (Luis Machado) Date: Wed, 01 Dec 2010 22:29:43 -0200 Subject: [Patches] [PATCH] Use lib/lib64 based on the libdir configure variable Message-ID: <1291249783.3774.10.camel@gargoyle> Hi, Python's build system (at least for 2.6.6) is not 32/64-bit aware in the sense that it always uses "lib" as the default lib/modules/config path. This patch handles this "problem" through the libdir configure variable. For example: --libdir=\${prefix}/lib64 --libdir=\${prefix}/lib This also changes the builtin paths that Python uses to look for lib/modules depending on what's set in the build. -------------- next part -------------- A non-text attachment was scrubbed... Name: py_libpath_fix.diff Type: text/x-patch Size: 10271 bytes Desc: not available URL: