<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE bugzilla SYSTEM "https://bugzilla.yoctoproject.org/page.cgi?id=bugzilla.dtd">

<bugzilla version="5.0.6"
          urlbase="https://bugzilla.yoctoproject.org/"
          
          maintainer="it-coreprojects-helpdesk@linuxfoundation.org"
>

    <bug>
          <bug_id>12703</bug_id>
          
          <creation_ts>2018-04-20 09:42:37 +0000</creation_ts>
          <short_desc>&quot;icc&quot; string in path, might lead to build errors.</short_desc>
          <delta_ts>2018-04-23 03:13:00 +0000</delta_ts>
          <reporter_accessible>1</reporter_accessible>
          <cclist_accessible>1</cclist_accessible>
          <classification_id>7</classification_id>
          <classification>Build System, Metadata &amp; Runtime</classification>
          <product>OE-Core</product>
          <component>core</component>
          <version>2.4.2</version>
          <rep_platform>x86</rep_platform>
          <op_sys>Multiple</op_sys>
          <bug_status>RESOLVED</bug_status>
          <resolution>WORKSFORME</resolution>
          
          
          <bug_file_loc></bug_file_loc>
          <status_whiteboard></status_whiteboard>
          <keywords></keywords>
          <priority>Undecided</priority>
          <bug_severity>enhancement</bug_severity>
          <target_milestone>---</target_milestone>
          
          
          <everconfirmed>1</everconfirmed>
          <reporter name="Riccardo">rmereu.dev</reporter>
          <assigned_to name="Ross Burton">ross.burton</assigned_to>
          <cc>costamagnagianfranco</cc>
    
    <cc>meta.mr.watcher</cc>
    
    <cc>meta.watcher</cc>
          
          
          <cf_os>---</cf_os>
          <cf_regression_type>---</cf_regression_type>
          
          <cf_docchange>Yes (doc changes required)</cf_docchange>

      

      

      

          <comment_sort_order>oldest_to_newest</comment_sort_order>  
          <long_desc isprivate="0" >
    <commentid>80361</commentid>
    <comment_count>0</comment_count>
    <who name="Riccardo">rmereu.dev</who>
    <bug_when>2018-04-20 09:42:37 +0000</bug_when>
    <thetext>This is a respin of bug 11592, building in folder path ~/Documents/Riccardo/Prova/poky/build causes the build itself to fail while compiling python3 recipe.
Moving to a lowercase only $PWD such as ~ made the same build succeed.
For some reasons python3 configure script is bailing-out while checking for gcc and detecting an unexisting icc (and then failing because of unknown $*FLAGS).

Please add a QA warning.

Attaching pastebin link with output

https://pastebin.com/6uYjQt0d</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80362</commentid>
    <comment_count>1</comment_count>
    <who name="Ross Burton">ross.burton</who>
    <bug_when>2018-04-20 09:54:05 +0000</bug_when>
    <thetext>11592 was related to packages with uppercase names, which breaks dpkg.

I always do builds in a directory with an uppercase letter in, so that isn&apos;t the problem.  Something else must have changed, resolving works for me.  Please file a new bug if you can reproduce on demand from a pristine configuration.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80363</commentid>
    <comment_count>2</comment_count>
    <who name="Gianfranco">costamagnagianfranco</who>
    <bug_when>2018-04-20 14:36:22 +0000</bug_when>
    <thetext>Hello, after doing some deeper research, I discovered that this isn&apos;t an upper case issue, but rather an
&quot;Do you have *icc* in your path name issue&quot;
Most likely this comes from some weird python3 configure issue, I&apos;ll debug it when I get a chance.

For now to reproduce just use icc as build directory.</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80366</commentid>
    <comment_count>3</comment_count>
    <who name="Gianfranco">costamagnagianfranco</who>
    <bug_when>2018-04-21 02:37:34 +0000</bug_when>
    <thetext>Ok, the problem is this one, and I crafted a quick and dirty patch
(this works assuming the compiler ends with gcc$ and not gcc-7$ or similar.

the stuff passed to --sysroot in $CC contained the *icc* string, adding the flags for icc compiler

CC=&apos;arm-poky-linux-gnueabi-gcc  -march=armv7ve -marm -mfpu=neon-vfpv4 -mfloat-abi=hard -mcpu=cortex-a7 -DNDEBUG -fno-inline --sysroot=/home/test/poky/icc-build-directory/tmp/work/cortexa7hf-neon-vfpv4-poky-linux-gnueabi/python3/3.5.3-r1.0/recipe-sysroot&apos;

Ross, do you think is sane to submit something like this to python folks?

--- a/configure.ac	2018-04-21 11:10:43.351156044 +0200
+++ b/configure.ac	2018-04-21 11:12:17.329798702 +0200
@@ -1318,11 +1318,11 @@ fi],
 [AC_MSG_RESULT(no)])
 if test &quot;$Py_LTO&quot; = &apos;true&apos; ; then
   case $CC in
-    *clang*)
+    *clang)
       # Any changes made here should be reflected in the GCC+Darwin case below
       LTOFLAGS=&quot;-flto&quot;
       ;;
-    *gcc*)
+    *gcc)
       case $ac_sys_system in
         Darwin*)
           LTOFLAGS=&quot;-flto&quot;
@@ -1382,7 +1382,7 @@ then
 fi
 LLVM_PROF_ERR=no
 case $CC in
-  *clang*)
+  *clang)
     # Any changes made here should be reflected in the GCC+Darwin case below
     PGO_PROF_GEN_FLAG=&quot;-fprofile-instr-generate&quot;
     PGO_PROF_USE_FLAG=&quot;-fprofile-instr-use=code.profclangd&quot;
@@ -1397,7 +1397,7 @@ case $CC in
       fi
     fi
     ;;
-  *gcc*)
+  *gcc)
     case $ac_sys_system in
       Darwin*)
         PGO_PROF_GEN_FLAG=&quot;-fprofile-instr-generate&quot;
@@ -1421,7 +1421,7 @@ case $CC in
         ;;
     esac
     ;;
-  *icc*)
+  *icc)
     PGO_PROF_GEN_FLAG=&quot;-prof-gen&quot;
     PGO_PROF_USE_FLAG=&quot;-prof-use&quot;
     LLVM_PROF_MERGER=&quot;true&quot;
@@ -1459,7 +1459,7 @@ then
 
         # Clang also needs -fwrapv
         case $CC in
-            *clang*) WRAP=&quot;-fwrapv&quot;
+            *clang) WRAP=&quot;-fwrapv&quot;
             ;;
         esac
 
@@ -1541,7 +1541,7 @@ yes)
     # ICC doesn&apos;t recognize the option, but only emits a warning
     ## XXX does it emit an unused result warning and can it be disabled?
     case &quot;$CC&quot; in
-    *icc*)
+    *icc)
     ac_cv_disable_unused_result_warning=no
     ;;
     *)
@@ -1796,7 +1796,7 @@ esac
 
 # ICC needs -fp-model strict or floats behave badly
 case &quot;$CC&quot; in
-*icc*)
+*icc)
     CFLAGS_NODIST=&quot;$CFLAGS_NODIST -fp-model strict&quot;
     ;;
 esac
@@ -2562,7 +2562,7 @@ then
 		else CCSHARED=&quot;-Kpic -belf&quot;
 		fi;;
 	IRIX*/6*)  case $CC in
-		   *gcc*) CCSHARED=&quot;-shared&quot;;;
+		   *gcc) CCSHARED=&quot;-shared&quot;;;
 		   *) CCSHARED=&quot;&quot;;;
 		   esac;;
 	esac
@@ -2603,7 +2603,7 @@ then
 			LINKFORSHARED=&quot;-Wl,--export-dynamic&quot;
 		fi;;
 	SunOS/5*) case $CC in
-		  *gcc*)
+		  *gcc)
 		    if $CC -Xlinker --help 2&gt;&amp;1 | grep export-dynamic &gt;/dev/null
 		    then
 			LINKFORSHARED=&quot;-Xlinker --export-dynamic&quot;
@@ -5233,7 +5233,7 @@ if test &quot;$have_gcc_asm_for_x87&quot; = yes; t
     # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=46491
     # http://gcc.gnu.org/ml/gcc/2010-11/msg00366.html
     case $CC in
-        *gcc*)
+        *gcc)
             AC_MSG_CHECKING(for gcc ipa-pure-const bug)
             saved_cflags=&quot;$CFLAGS&quot;
             CFLAGS=&quot;-O2&quot;</thetext>
  </long_desc><long_desc isprivate="0" >
    <commentid>80376</commentid>
    <comment_count>4</comment_count>
    <who name="Gianfranco">costamagnagianfranco</who>
    <bug_when>2018-04-23 03:13:00 +0000</bug_when>
    <thetext>I opened an upstream bug report
https://bugs.python.org/issue33341</thetext>
  </long_desc>
      
      

    </bug>

</bugzilla>