Blame view

buildroot/buildroot-2016.08.1/package/python3/0009-Don-t-add-multiarch-paths.patch 1.33 KB
6b13f685e   김민수   BSP 최초 추가
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
  From bac5ac529cc0902a340a5cd03308433c6e80d1f6 Mon Sep 17 00:00:00 2001
  From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
  Date: Wed, 23 Dec 2015 11:36:27 +0100
  Subject: [PATCH] Don't add multiarch paths
  
  The add_multiarch_paths() function leads, in certain build
  environments, to the addition of host header paths to the CFLAGS,
  which is not appropriate for cross-compilation. This patch fixes that
  by simply removing the call to add_multiarch_paths() when we're
  cross-compiling.
  
  Investigation done by David <buildroot-2014@inbox.com>.
  
  Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
  ---
   setup.py | 2 +-
   1 file changed, 1 insertion(+), 1 deletion(-)
  
  diff --git a/setup.py b/setup.py
  index 24a7153..8380a64 100644
  --- a/setup.py
  +++ b/setup.py
  @@ -474,10 +474,10 @@ class PyBuildExt(build_ext):
           if not cross_compiling:
               add_dir_to_list(self.compiler.library_dirs, '/usr/local/lib')
               add_dir_to_list(self.compiler.include_dirs, '/usr/local/include')
  +            self.add_multiarch_paths()
           # only change this for cross builds for 3.3, issues on Mageia
           if cross_compiling:
               self.add_gcc_paths()
  -        self.add_multiarch_paths()
   
           # Add paths specified in the environment variables LDFLAGS and
           # CPPFLAGS for header and library files.
  -- 
  2.6.4