10 Replies Latest reply on Sep 9, 2016 4:29 PM by marcuso

    Cant build examples for D2000 - Wont build app_entry.o

    marcuso

      Hi,

       

      I cant build the examples I get this error (and app_entry.o doesn't get built but main.o does)

       

      14:46:17 **** Incremental Build of configuration Release for project Ex1 ****

      make

      APP_NAME = Ex1

      SOC = quark_d2000

      TARGET = x86

      APP_DIR = .

      BUILD = release

      CSTD = c99

      VERSION = '1.1.0'

      MARCUS !! Version defined

      MARCUS 2 !!

      MARCUS PRE prepre sys.mk !!

      MARCUS PRE sys.mk !!

      MARCUS sys.mk !!

      MARCUS quark.mk !!

      MARCUS About to link!!

      make -C ./bsp/drivers SOC=quark_d2000 TARGET=x86 BUILD=release V=0 CSTD=c99

      BUILD = release

      CSTD = c99

      VERSION = '1.1.0'

      MARCUS !! Version defined

      MARCUS 2 !!

      MARCUS drivers.mk !!

      MARCUS quark.mk !!

      make[1]: Entering directory `C:/IntelSWTools/ISSM_2016.1.067/workspace/Ex1/bsp/drivers'

      make[1]: Leaving directory `C:/IntelSWTools/ISSM_2016.1.067/workspace/Ex1/bsp/drivers'

      CC release/quark_d2000/x86/obj/main.o

      /usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'

      /usr/bin/sh: -c: line 1: syntax error: unexpected end of file

      make: *** [release/quark_d2000/x86/obj/"."/app_entry.o] Error 258

       

      14:46:47 Build Finished (took 29s.591ms)

        • 1. Re: Cant build examples for D2000 - Wont build app_entry.o
          Intel_Alvarado

          Hi,

           

          Are you still running the tests on Windows 10? Could you post screenshots of the steps you took that led you to this error? We tested the Hello World on Windows 8.1 and didn’t see this issue.

           

          -Sergio

          • 2. Re: Cant build examples for D2000 - Wont build app_entry.o
            marcuso

            Yes I'm running on windows 10. Are you aware that permissions have changed significantly in Windows 10 ? This OS is much stricter about default ownership of resources ie folders. So I think if you run on windows 10 (its free to upgrade) you will see similar issues.

             

            The steps Im taking are really very straight forward.

             

            1. Clean install of ISS

            2. Run ISS via iss_mcu_ide_eclipse-launcher.bat (either double click from GUI or run via cmd.exe same results, even tried Run as admin from GUI context menu (right click) same results

            3. When elcipse starts - select recommended - default workspace folder (C:\IntelSWTools\ISSM_2016.1.067\workspace)

            4. From start page in eclispe - Click on File -> New -> Intel project  for Microcontrollers

            5. Wizard starts -> Select Intel Quark D2000 Dev Board -> Next

            6. Select Intel QMSI (1.1) -> Next

            7. Left defaults - Onboard USB -> Next

            8. Name of project dave - select Hello World example - Finishd20001.png

            9. I dont change any files at all, and see that the project is displayed OK

            d20002.png

            10. Click the hammer icon on the tool bar - build debug config - fails to build with 2 errors

             

            Here is the build output (note that release config is the same)d20003.png

             

             

            d20004.png

             

             

            There build output from the console view (with errors)...

             

            13:49:05 **** Build of configuration Debug for project dave ****

            make

            APP_NAME = dave

            SOC = quark_d2000

            TARGET = x86

            APP_DIR = .

            BUILD = debug

            CSTD = c99

            VERSION = '1.1.0'

            make -C ./bsp/drivers SOC=quark_d2000 TARGET=x86 BUILD=debug V=0 CSTD=c99

            BUILD = debug

            CSTD = c99

            VERSION = '1.1.0'

            make[1]: Entering directory `C:/IntelSWTools/ISSM_2016.1.067/workspace/dave/bsp/drivers'

            CC ../drivers/debug/quark_d2000/x86/obj/clk.o

            Assembler messages:

            Fatal error: can't create ../drivers/debug/quark_d2000/x86/obj/clk.o: No such file or directory

            make[1]: *** [../drivers/debug/quark_d2000/x86/obj/clk.o] Error 1

            make: *** [libqmsi] Error 2

            make[1]: Leaving directory `C:/IntelSWTools/ISSM_2016.1.067/workspace/dave/bsp/drivers'

             

            13:49:24 Build Finished (took 18s.675ms)

             

            Can't get more detailed than that ! You are aware that the errors are caused by make not having permissions to use "mkdir" aren't you ? I keep mentioning this, Windows 10 permissions will cause this. These errors go away when I manually create the folders that make can not generate. Then it goes to the errors mentioned above (top of this thread)

             

            Marcus

            • 3. Re: Cant build examples for D2000 - Wont build app_entry.o
              marcuso

              I even tried to create a workspace under my own user folder space - ie C:\Users\mobrien\newworkspace\ and I still got the same problem.

              • 4. Re: Cant build examples for D2000 - Wont build app_entry.o
                marcuso

                I then tried to install the ISS in my own area C:\Users\mobrien\Desktop\ISS  then ran ISS and same errors. (even running this new install as admin).

                • 5. Re: Cant build examples for D2000 - Wont build app_entry.o
                  marcuso

                  OK I have a fix for you, change all your .mk files from this type of statement

                   

                      $(call mkdir -p, $(DRV_DIR)/$(BUILD)/$(SOC)/$(TARGET)/$(OBJ))

                   

                  To this one (take off call and the coma)

                   

                  mkdir -p $(DRV_DIR)/$(BUILD)/$(SOC)/$(TARGET)/$(OBJ)

                   

                  I changed all the .mk files

                   

                  This way the "call" doesn't change the user. This works up to the point of...

                   

                  BUT I STILL END up with this error

                   

                   

                  14:40:20 **** Incremental Build of configuration Debug for project Hello_World ****

                  make

                  APP_NAME = Hello_World

                  SOC = quark_d2000

                  TARGET = x86

                  APP_DIR = .

                  BUILD = debug

                  CSTD = c99

                  VERSION = '1.1.0'

                  MARCUS Hello about to make the folders - mkdir

                  MARCUS DONE IT

                  make -C ./bsp/drivers SOC=quark_d2000 TARGET=x86 BUILD=debug V=0 CSTD=c99

                  BUILD = debug

                  CSTD = c99

                  VERSION = '1.1.0'

                  MARCUS in bsp drivers now

                  MARCUS in bsp drivers about to mkdirs

                  make[1]: Entering directory `C:/Users/mobrien/Desktop/ISS/ISSM_2016.1.067/workspace/Hello_World/bsp/drivers'

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  mkdir -p ../build/debug/quark_d2000/x86/libqmsi/include

                  make[1]: Leaving directory `C:/Users/mobrien/Desktop/ISS/ISSM_2016.1.067/workspace/Hello_World/bsp/drivers'

                  mkdir -p ./debug/quark_d2000/x86/obj

                  CC debug/quark_d2000/x86/obj/main.o

                  mkdir -p ./debug/quark_d2000/x86/obj/"."

                  /usr/bin/sh: -c: line 0: unexpected EOF while looking for matching `"'

                  /usr/bin/sh: -c: line 1: syntax error: unexpected end of file

                  make: *** [debug/quark_d2000/x86/obj/"."/app_entry.o] Error 258

                   

                  14:40:43 Build Finished (took 23s.137ms)

                  • 6. Re: Cant build examples for D2000 - Wont build app_entry.o
                    Intel_Alvarado

                    Thank you for providing these steps. We’ve have only tested this scenario using Windows 8.1, we’ll run the test on Windows 10 and report our results back to you. Thank you for your patience.

                     

                    -Sergio

                    • 7. Re: Cant build examples for D2000 - Wont build app_entry.o
                      Mike Hibbett

                       

                       

                       

                       

                       

                       

                       

                       

                       

                       

                       

                      • 8. Re: Cant build examples for D2000 - Wont build app_entry.o
                        MichelleC_Intel

                        Apologies for the delay getting back on this issue - If you are still having issues can you please try this workaround.

                         

                        Update the PATH settings at the end of the  C:/IntelSWTools/ISSM_2016.1.067/issm_env.bat to :

                         

                        ::

                        :: Extend PATH with ISSM tools

                        ::

                        set PATH=C:\WINDOWS\System32\Wbem

                        set PATH=%ISSM_UTILS_ROOT%;%ISSM_TOOLCHAIN_BIN%/;%ISSM_TOOLCHAIN_UTILS%;%ISSM_TOOLS_ROOT%/python;%PATH%

                         

                         

                        Resstart ISSM and try building your project.

                         

                        -- Michelle.

                        • 9. Re: Cant build examples for D2000 - Wont build app_entry.o
                          Intel_Alvarado

                          Hi Marcus,

                           

                          Do you still need assistance with this thread?

                           

                          -Sergio

                          • 10. Re: Cant build examples for D2000 - Wont build app_entry.o
                            marcuso

                            Thanks to