This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Title: Look for local sqlite3 by parsing -I/-L flags in linux as well.
Type: Stage: resolved
Components: Build Versions: Python 3.6
Status: closed Resolution: duplicate
Dependencies: Superseder: Python build should check CPATH, C_INCLUDE_PATH for module dependencies
View: 21571
Assigned To: Nosy List: ned.deily, yesimon
Priority: normal Keywords: patch

Created on 2015-04-03 14:36 by yesimon, last changed 2022-04-11 14:58 by admin. This issue is now closed.

File name Uploaded Description Edit
sqlite_patch.diff yesimon, 2015-04-03 14:36 review
Messages (3)
msg239997 - (view) Author: Simon Ye (yesimon) * Date: 2015-04-03 14:36
Based off of

Currently building python on linux only looks for sqlite include paths in a hardcoded set of system paths, but if the user specifies -I/-L options during compilation, python looks there for sqlite3 as well, but only on OS X. This is problem for people who want to build python against a local version of sqlite3, and it is also inconsistent with the OS X behavior. Also the comments say that it should work on any unix-y OS!
msg239998 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2015-04-03 14:52
This is essentially a duplicate of Issue3467 and various other similar issues.  While it may not be easy to justify the special case in for OS X (the reason was primarily for OS X installer builds), it would be even harder to justify adding another special case just for "Linux" systems.  Why not all platforms and libs?  The standard reply (in Issue3467 and elsewhere) to these kinds of requests has been to use one of the Modules/Setup files (like Setup.local) to customize extension module builds or to come up with a more general solution for the top-level third-party library configuration, rather than more special cases for each lib.
msg239999 - (view) Author: Ned Deily (ned.deily) * (Python committer) Date: 2015-04-03 15:01
My apologies, I replied a bit too hastily, thinking incorrectly that your suggested change was just for sqlite3.  While the comments above still apply, there is already an open request for the more general feature (and more) under Issue21571.  So I suggest further discussion be moved there.
Date User Action Args
2022-04-11 14:58:15adminsetgithub: 68046
2015-04-03 15:01:40ned.deilysetsuperseder: sqlite3 path is hard coded in -> Python build should check CPATH, C_INCLUDE_PATH for module dependencies
messages: + msg239999
2015-04-03 14:52:23ned.deilysetstatus: open -> closed

superseder: sqlite3 path is hard coded in

nosy: + ned.deily
messages: + msg239998
resolution: duplicate
stage: resolved
2015-04-03 14:36:42yesimoncreate