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.

classification
Title: Need setup.py to pick up -isystem flags from CPPFLAGS
Type: enhancement Stage: patch review
Components: Cross-Build Versions: Python 3.9, Python 3.8
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: Alex.Willmer, jherland
Priority: normal Keywords: patch

Created on 2019-08-05 15:10 by jherland, last changed 2022-04-11 14:59 by admin.

Pull Requests
URL Status Linked Edit
" from $CPPFLAGS">PR 15136 open jherland, 2019-08-05 15:15
Messages (1)
msg349054 - (view) Author: Johan Herland (jherland) * Date: 2019-08-05 15:10
First time contributor here, still learning the ropes.

We're cross-compiling python in an environment where we set up CPPFLAGS, LDFLAGS, etc. to point directly to the locations where we have built Python's dependencies. For example, we will typically build Python in an environment that includes:

  CPPFLAGS=\
    -isystem /path/to/ncurses/build/include \
    -isystem /path/to/libffi/build/include \
    -isystem /path/to/zlib/build/include \
    -isystem /path/to/openssl/build/include \
    -isystem /path/to/readline/build/include
  
  LDFLAGS=\
    -L/path/to/ncurses/build/lib \
    -L/path/to/libffi/build/lib \
    -L/path/to/zlib/build/lib \
    -L/path/to/openssl/build/lib \
    -L/path/to/ciscossl-fom/build/lib \
    -L/path/to/readline/build/lib

setup.py already picks up our -L options from LDFLAGS and propagates them into the build commands, but the -isystem options from CPPFLAGS are currently ignored.

I will post a PR that teaches setup.py to handle -isystem options in CPPFLAGS the same way it currently handles -I options.
History
Date User Action Args
2022-04-11 14:59:18adminsetgithub: 81944
2019-08-05 15:15:28jherlandsetkeywords: + patch
stage: patch review
pull_requests: + pull_request14874
2019-08-05 15:10:05jherlandcreate