Studio 7 & WIN 10 Buils fail on make error 127

Go To Last Post
7 posts / 0 new
Author
Message
#1
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Do you the issue of this error?

 

"C:\Program Files (x86)\Atmel\Atmel Toolchain\AVR8 GCC\Native\3.4.1061\avr8-gnu-toolchain\bin\avr-gcc.exe" -x c -funsigned-char -funsigned-bitfields -DDEBUG -O1 -ffunction-sections -fdata-sections -fpack-struct -fshort-enums -mrelax -g2 -Wall -mmcu=atmega128 -c -std=gnu99 -MD -MP -MF "Battery.d" -MT"Battery.d" -MT"Battery.o" -o "Battery.o" ".././Battery.c"

/usr/bin/sh: C:\Program Files (x86)\Atmel\Atmel Toolchain\AVR8 GCC\Native\3.4.1061\avr8-gnu-toolchain\bin\avr-gcc.exe: command not found

make: *** [Battery.o] Error 127

Done executing task "RunCompilerTask" -- FAILED.

Done building target "CoreBuild" in project "DomoHouseV6.cproj" -- FAILED.

Done building project "DomoHouseV6.cproj" -- FAILED.

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Somehow it looks like you have sh running the command...

/usr/bin/sh

Also, an old avr8 toolchain? The toolchain invoked there does not seem to be the one from studio 7. Is this a custom makefile?

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

Thanks:

 

After the first upgrade to studio 7 and WIN 10 all the build issues is ok with all my projects (OK also with studio 6.2) This bug happen this week .

 

"Is this a custom makefile?" not It is not a custom makefile

I have not run the sh command

 

I have dawnload the last STUDIO 7 upgrade but i have the same issue.

in the tool option page : C:\Program Files (x86)\Atmel\Studio\7.0\toolchain\avr8\avr8-gnu-toolchain\bin

The last line of the  makefile after ​the files list is:

 

OUTPUT_FILE_PATH +=DomoHouseSolution_V6.elf

OUTPUT_FILE_PATH_AS_ARGS +=DomoHouseSolution_V6.elf

ADDITIONAL_DEPENDENCIES:=

OUTPUT_FILE_DEP:= ./makedep.mk

LIB_DEP+=

LINKER_SCRIPT_DEP+=

# AVR32/GNU C Compiler

 

The build of an legacy project with studio 6.2 is ok.

If I create a new project with the same files (A copy of the file of this legacy project in a new directory) he buildis not ok (Error 127). The new project creation provide this  general wraning : could not read project specific software Framework configuration setting  from 'essaiV-6' System.runtime.InteropServices.COMExeption: ,MethodName : get_ActiveConfiguration #AVR32 GNU C COMPILER

 

Now I remember : This week to make a new version of an legacy project I have made a copy of the *.C file , *.h file and the Old "Solution file" (Studio 6.1..) in a new folder (the solution file have the same icon that the *.c file since studio 7) a new build of this legacy project, before upgrade) with the legagy solution file in the "solution project" provide an error, then i have delated the "solution file" fron this new project. May be this mistake had provide this bug!

 

 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Hmh, could you post the full build log...

:: Morten

 

(yes, I work for Atmel, yes, I do this in my spare time, now stop sending PMs)

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

 

Yes, the build of the new project with the make error 127 provide only two file in the debug folder see MakeFileFromEssai.zip

 

MakefileFromEssai.zip and legacyprojectWithouterror.zip was two build with the same files ..

 

..without error an legacy project from 6.2 with any upgrade build with studio 6.2

...fromEssai the same lecagy project copy in a new folder to make a new project check (provide the error127) build with studio 6.2 (Idem with studio 7)

 

Thanks for your help

Attachment(s): 

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I think of having found the solution, it is a corruption of the window register. After a cleaning with Registry Reveiver ( who find more than 2000 Errors) the compilation of a new project is possible with studio 6.2, but not yet studio 7, I am going to have to reinstall studi07.

  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

After a lot of work (and days) to clean the WINDOW registers bank , the remove of Studio (6.x and 7), all the "ATMEL " directories and all the "ATMEL" utilities. Studio 7 run and build without fix

 

For example after a Window Register clean up,  an new installation / remove of studio 6.2 leaves approximately 50 errors in window register.