[issue1706863] Failed to build Python 2.5.1 with sqlite3

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: I've committed "fix_sqlite3_setup_error.patch" in r66766. I think the problem disutils cannot recognize .dll.a as library on cygwin is another issue, so I'll open new tracker item. -- resolution: -> fixed status: open -> closed _

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: -- keywords: -needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-b

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Roumen Petrov <[EMAIL PROTECTED]> added the comment: no objections ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bugs-list mailing lis

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: >extra changes that has to go in a >specific compiler class. As example platform can be any but compiler >gcc(mingw) that produce executables for windows host platform. You are right. It should be. My patch is just one choice when switchin

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Jason Tishler <[EMAIL PROTECTED]> added the comment: Hirokazu Yamamoto wrote: > Umm, it works, but I'm not sure we can call import library as > dylib... Agreed. > I had considered attached patch "experimental_distutils.patch". > It's little adhoky, I'm not sure this patch is acceptable. The ne

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Roumen Petrov <[EMAIL PROTECTED]> added the comment: About experimental_distutils.patch - extra changes that has to go in a specific compiler class. As example platform can be any but compiler gcc(mingw) that produce executables for windows host platform. In this case search has to include suffix

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: >So, is my patch acceptable? Umm, it works, but I'm not sure we can call import library as dylib... If it's not problem, I think your patch is fine. # I had considered attached patch "experimental_distutils.patch". It's little adhoky, I'm

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Jason Tishler <[EMAIL PROTECTED]> added the comment: Hirokazu Yamamoto wrote: > Python is not using CCygwinCCompiler to build itself on cygwin. Which I why my patch modifies UnixCCompiler instead of CCygwinCCompiler. FWIW, my patch leverages the already existing Cygwin specific code in UnixCC

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Roumen Petrov <[EMAIL PROTECTED]> added the comment: If Jason patch resolve issue may I ask cygwincompiler.py to be modified too just in case if as result of issue2445 is decided to switch back ? ___ Python tracker <[EMAIL PROTECTED]>

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: Python is not using CCygwinCCompiler to build itself on cygwin. See issue2445. ___ Python tracker <[EMAIL PROTECTED]> ___ ___

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Amaury Forgeot d'Arc <[EMAIL PROTECTED]> added the comment: +1 for adding dylib_lib_extension = ".dll.a" to the CygwinCCompiler class. -- nosy: +amaury.forgeotdarc ___ Python tracker <[EMAIL PROTECTED]> __

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Roumen Petrov <[EMAIL PROTECTED]> added the comment: I think that modification has to be in cygwinccompiler. It is specific for win32 binutils and impact both - cygwin and mingw. ___ Python tracker <[EMAIL PROTECTED]> __

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Jason Tishler <[EMAIL PROTECTED]> added the comment: The Cygwin build issue was worked around by releasing a sqlite3 package that contains a static library too. However, this causes the Python _sqlite module to be statically linked against sqlite3 even though a shared library version is availa

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Roumen Petrov <[EMAIL PROTECTED]> added the comment: The search for *dll.a is described in paragraph "direct linking to a dll" here: http://sourceware.org/binutils/docs/ld/WIN32.html -- nosy: +rpetrov ___ Python tracker <[EMAIL PROTECTED]>

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Changes by Hirokazu Yamamoto <[EMAIL PROTECTED]>: -- keywords: +needs review ___ Python tracker <[EMAIL PROTECTED]> ___ ___ Python-bu

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Hirokazu Yamamoto <[EMAIL PROTECTED]> added the comment: >AttributeError: 'NoneType' object has no attribute 'rfind' Fixing this error is not difficult. I think attached patch is enough. But still cygwin user who wants to use sqlite3 module won't be happy. find_library() supports static lib, sh

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Jason Tishler <[EMAIL PROTECTED]> added the comment: The Cygwin build is having the same problem: http://cygwin.com/ml/cygwin/2008-09/msg00145.html In this case, the sqlite3 libraries are installed (in /usr/lib), but their suffixes do not match the expected values. Does anyone know the best w

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Eh Tan added the comment: The problem is at line 890, setup.py, r60970. sqlite_libfile = self.compiler.find_library_file( sqlite_dirs_to_check + lib_dirs, 'sqlite3') sqlite_libdir = [os.path.abspath(os.path.dirname(sqlite_libfile))]

[issue1706863] Failed to build Python 2.5.1 with sqlite3

Gerhard Häring added the comment: This is apparently a problem in setup.py. There seems to be a code path where an object should be a string, but is None instead. I'll have to review the relevant parts of setup.py. -- nosy: +ghaering type: -> compile error _