classification
Title: Use CFLAGS when extracting multiarch
Type: enhancement Stage:
Components: Build Versions: Python 3.5
process
Status: open Resolution:
Dependencies: Superseder:
Assigned To: Nosy List: barry, doko, martin.panter, pitrou
Priority: normal Keywords:

Created on 2014-12-02 16:20 by pitrou, last changed 2016-07-13 03:16 by martin.panter.

Messages (2)
msg232013 - (view) Author: Antoine Pitrou (pitrou) * (Python committer) Date: 2014-12-02 16:20
This patch fixes MULTIARCH computation when using CFLAGS=-m32:

diff --git a/configure b/configure
--- a/configure
+++ b/configure
@@ -5402,7 +5402,7 @@ hp*|HP*)
     esac;;
 esac
 
-MULTIARCH=$($CC --print-multiarch 2>/dev/null)
+MULTIARCH=$($CC $CFLAGS --print-multiarch 2>/dev/null)
 
 
 
diff --git a/configure.ac b/configure.ac
--- a/configure.ac
+++ b/configure.ac
@@ -788,7 +788,7 @@ hp*|HP*)
     esac;;
 esac
 
-MULTIARCH=$($CC --print-multiarch 2>/dev/null)
+MULTIARCH=$($CC $CFLAGS --print-multiarch 2>/dev/null)
 AC_SUBST(MULTIARCH)
msg270293 - (view) Author: Martin Panter (martin.panter) * (Python committer) Date: 2016-07-13 03:16
Why do you set CFLAGS=-m32? When I cross-compile a 32-bit Python on a 64-bit host, I set CC="gcc -m32" instead. (Otherwise, I would have to specify LDFLAGS="-m32" as well.)
History
Date User Action Args
2016-07-13 03:16:56martin.pantersetnosy: + martin.panter
messages: + msg270293
components: + Build
2014-12-02 16:20:30pitroucreate