Windows 8.1 compilation error

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

Hi

After upgrading Windows 8(64bit)to 8.1 version, when try to compile project in AvrStudio 4 (WINAVR20100110) I get error:

0 [main] sh 2312 sync_with_child: child 4744(0x14C) died before initialization with status code 0xC0000142
73796 [main] sh 2312 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
rm -rf main.o test.elf dep/* test.hex test.eep test.lss test.map
make: [clean] Error -1073741502 (ignored)
Build succeeded with 0 Warnings...
0 [main] sh 1484 sync_with_child: child 2300(0x14C) died before initialization with status code 0xC0000142
64185 [main] sh 1484 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
avr-gcc -mmcu=atmega644pa -Wall -gdwarf-2 -std=gnu99 -DF_CPU=3686400UL -Os -funsigned-char -funsigned-bitfields -fpack-struct -fshort-enums -MD -MP -MT main.o -MF dep/main.o.d -c ../main.c
../main.c:57: fatal error: opening dependency file dep/main.o.d: No such file or directory
compilation terminated.
make: *** [main.o] Error 1
Build failed with 1 errors and 0 warnings...

Before Windows upgrading compilation was correct.

Please help

Sebastian

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

What happens with AS6.1 that also includes a much more recent avr-gcc?

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

I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)

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

Having the same issue here on Win8.1 and the above does not solve it for me. AS 6.1 installed, 6.1.2730 SP2

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

sebastor wrote:
I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)

Sebastor, Ty alot. I had the same problem, but i solved using your tips!

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

the solution doesnt work for windows 8.1.
please help!!

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

The file fixed the error for me in Windows 8.1 Studio 6.1.

Thank you

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

sebastor wrote:
I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)


Thanks, worked on windows 8 64 bits.

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

Thanks. This fixed my compilation error. I am using AVR studio 4.16 by requirement. I first loaded in studio 4 and gcc 2007. I got no compilation errors but I could not usb link to the AVR Dragon and found no reliable method to fix that. Thinking that problem was fixed in ATMEL Studio 6, I went ahead and did a complete load. Bingo -- fixed the USB driver problem but introduced the compiler problem others seem to have here. After loading the dll found on the link in this thread, now I am a happy camper.

I am running windows 8.1 on a Dell Laptop.

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

thank's

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

Thanks, The file fixed my compilation error, on windows 8.1 pro

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

Thank you so much, this worked for me on windows 8.1

Very easy fix.

:D

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

Thankyou!!

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

Thank you so much for this!! It worked for me on Windows 8.1!

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

Thank you !

Your solution worked for me.

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

Worked for me too. Thanks!

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

Thanks a lot. It worked on my windows 8.1. I'm now able to compile programs. But now I got this error after compilation. (Tool -> [WinAVR] Program )

avrdude -p atmega8 -P lpt1 -c bsd    -U flash:w:main.hex 
avrdude: can't open device "giveio"

avrdude: failed to open parallel port "lpt1"

make.exe: *** [program] Error 1

 

Please help.

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

> "make.exe" all
      0 [main] sh 796 sync_with_child: child 4948(0x14C) died before initialization with status code 0xC0000142
  46604 [main] sh 796 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable
      0 [main] sh 4856 sync_with_child: child 3604(0x14C) died before initialization with status code 0xC0000142
  11638 [main] sh 4856 sync_with_child: *** child state waiting for longjmp
/usr/bin/sh: fork: Resource temporarily unavailable

-------- begin --------
avr-gcc (WinAVR 20100110) 4.3.3
Copyright (C) 2008 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

make.exe: *** No rule to make target `main.elf', needed by `elf'.  Stop.

> Process Exit Code: 2
> Time Taken: 00:01

 I am having this problem. can some one please help me understand what's going on.

Tried the above method, but it is not working.

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

Worked for me in win 8.1

Thanks

--waruna

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

Thanks a lot! It worked

 

Anoop

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

I too faced this issue with Windows 8.1 and the solution suggested did not work.

But I seem to have solved the issue with MHV AVR Tools (replacement for WinAVR).

 

MHV AVR tools is well maintained (currently AVR-GCC 4.8.2 and AVRdude 6.0), so is to be preferred over WinAVR.

 

**If using WinAVR, also there is a solution below**:

(I uninstalled winAVR and installed MHV AVR tools from
:https://infernoembedded.com/sites/default/files/project/MHV_AVR_Tools_20131101.exe
 )

and :

1. Installed Mingw-32 from here :

     http://sourceforge.net/projects/mingw/files/latest/download?source=files

 

**If using winAVR, copy "C:\MinGW\msys\1.0\bin\msys-1.0.dll" to util/bin folder of WinAVR, that's all! **

**If using MHV, read on **

2. I manually added "C:\MinGW\bin" and "C:\MinGW\msys\1.0\bin" to the
environment PATH.   It is advisable to restart your PC now to ensure the newly added PATHs are effective.

3.Now make clean / make all works fine (my makefiles are based on the
sample supplied with WinAVR).

4. avrdude 6.0 is included with MHV AVR tools and seems to work,
though I've yet to test it with actual projects.

 

Thank you.

Last Edited: Sun. Mar 29, 2015 - 04:32 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

I get this from your page.

 

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Hi,

 

Strange, my browser (IE 11)  gave no such warning !

 

 

Perhaps its just bad website design, and Firefox doesn't like it ?

 

I would ignore and proceed, since the site or downloaded exe does not require you to register, or enter any personal details.

 

The downloaded exe can easily be scanned by any anti-virus program ...  

 

But you can refer to this AVR freaks thread :

 

https://www.avrfreaks.net/comment/701224#comment-701224

 

and also  the download page (shown above) :

 

https://infernoembedded.com/products/avr-tools/release

 

though I dare say you will get that warning again.

 

 

Last Edited: Sun. Mar 29, 2015 - 08:16 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

MHV AVR Tools (replacement for WinAVR).

So just to be clear here. Are you saying that if one is using AS4.x and winAvr one can replace the later with the MHV AVR tools and Studio will happily work as if winAvr was used?

 

What advantages are there in this? Is this package supporting newer or latest AVR chips not supported by winAvr?

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

This thread is about getting winAVR (or any other AVR GCC tool chain) to work with windows 8.1. It all started with trying to find a solution to make.exe supplied with winAVR failing under win 8.1. I tried the the fix presented earlier in this thread, but that didn't work, so my search led me to my present solution. Ever since winAVR died, I have "upgraded"_it by downloading the tool chain from Atmel and overwriting the old files inside winAVR with these (I wanted to avoid Atmel studio). But after installing Windows 8.1, Make from winAVR stopped working, so I was forced to try out other solutions, concluding with the solution I outlined previously. WinAVR is now defunct and the last avr GCC version packaged with it is 4.3 (I think) latest release from Atmel is 4.8.1. The latest release does offer some extra features like declaring variables in flash (using __flash qualifier) besides the inevitable optimisation improvement (to answer your question) The advantage of this is I can once again work with avrGCC in windows 8.1, without having to rely on Atmel studio :)

Last Edited: Sat. Apr 11, 2015 - 07:09 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

make.exe supplied with winAVR failing under win 8.1.

So is Win8.x as bad as I thought? I have jut got a new computer and installed Win7 ultimate.  AS4.18 and winAvr work well with that.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Yes, I never had a problem using make with windows 7.
But then I guess it's winAVR that got stuck, while
The world moved on ...
The bright side is that I now have a toolchain that will hopefully work for at least the next couple of windows versions. :)

Last Edited: Mon. Mar 30, 2015 - 01:46 AM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

hmm I have been messing around with the toolchain and a couple of other files and now I have XmegaE5 support in C (had it already in ASM) with AS4.18. smiley

 

Now to try and get JTAG Mk2 support for programming and debugging....

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

sebastor wrote:

I found solution.

Copy this file:

http://www.madwizard.org/download/electronics/msys-1.0-vista64.zip

to utils\bin directory (WinAVR)

 

It helps a lot! I've signed up this new account specifically to say thanks!

 

/******************************/

 

Well, my winavr @ win8.1x86 cannot compile my prj, you know, popping out sth with error code "0xc0000142". I spent all night working to figure it out. And finally, I googled and found this brilliant forum. Problem solved. Thanks again!

Last Edited: Sat. Apr 11, 2015 - 01:18 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

It helps a lot!

 That's great but please explain a bit more or one would think that you are trying your hand at spamming the place.

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Installation of the useless 'msys-1.0-vista64.zip'.
Error occurs continuously intermittently.

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

Installation of the useless 'msys-1.0-vista64.zip'.
Error occurs continuously intermittently.

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

Error occurs continuously intermittently

Well at least that is better than an error occurring intermittently continuously.

 

David 

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

Installation of the useless 'msys-1.0-vista64.zip'.
Error occurs continuously intermittently.

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

This worked for me! Thanks!

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

Thank you sooo very much.. 

 

i am using windows 8.1 on lenovo, the solution worked.

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

sebastor wrote:

I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)

 

Thanks it work fine on windows 10 too!

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

thank you very very very much
from 4 hrs i was having this problem 
but i am using windows8

 

BE student of Electronics and Telecommunication 

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

sebastor wrote:

I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)

 

solved issue for windows-10. 

---

Saurav Shandilya

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

Thank you. It works.

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

solved on Wista 64

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

Thank U.works fine in windows 10.

manoj

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

Thanks!! msys-1.0.dll file already was there so I just replaced it and it worked. laugh

 

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

I am having this issue and found this thread. I really wonder if its really a solution or some BS?

Not willing to give it a try since a bunch of first timers recommended it.

Still looking for a solution.

 

If you are reading this and you don't think it smells funny I might revisit your security state of mind.

 

 

 

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

The msys dll thing was an issue with WinAVR. It was a valid solution at the time.

 

But why in 2016 is anyone using WinAVr (last release January 2010). The avr-gcc compiler has moved on since then. The latest release built by Atmel is 4.9.2 and the really adventurous can even pull the source for 5.0+ and build that.

 

So yeah, apply the msys dll fix if you are using old tools on a modern operating system. Or the simpler answer (to me at least) is to use a 2015 compiler.

 

(as you may notice I have a few posts here and have been around a while and watched all this flood past a few years ago when it was actually relevant ;-)

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

thank you sooo much smiley

have you any fb id?

 

 

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

I have no idea what "fb id" means?!?

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

With my FB I hat on he wants to share your life on Facebook!

John Samperi

Ampertronics Pty. Ltd.

www.ampertronics.com.au

* Electronic Design * Custom Products * Contract Assembly

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

Works with Win10 x64 too!

 

Thanks guys!

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

Its not working for mi I'm using avr studio 4.16 n lenovo lapy with w10 winavr 20100110
Plz give solution

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

Thanks!

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

thanks a lot. the problem solved as stated.

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

The dll works for me too ... I'm using Windows 10 and after migrating from Win 7-64 bit had the problem that was described here ... after ferreting around for a bit I gave it a whirl and it seems to restore the project build sequences to their correct functioning.

 

Thanks for getting me out of the hole!

 

Mike

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

hello,

../ledblink.c:14: fatal error: opening dependency file dep/ledblink.o.d: No such file or directory

i am getting this error for windows 10. I am new to the programming. Please help me out.

 

shree

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

Try a "clean" first.

 

The way this works is that the first time you build the compiler generates a map of all the .h files involved and creates .d (dependency) lists. On subsequent "make" it checks the times on all the .h so that if any have changed it triggers the .c to rebuild even if it hadn't changed itself. But if there's some problem in this process you see the kind of error you are getting above. Usually a "clean" which wipes everything so it all starts from scratch is enough to rectify things.

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

hello clawson,

thanks for your advice. You told me to clean it. how can i do that cleaning work, please guide me.

shree

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

If using Studio on the build menu - should be a "clean" entry. If building at a command line "make clean"

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

 

thank you clawson, I done with clean up, but then also error remain as it is. after cleaning it gives me following msg. Attachement contains error msg and a screen shots. please down load the attachment n help me.

 

 

 

 

Attachment(s): 

shree

Last Edited: Sat. Oct 29, 2016 - 12:27 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

OMG WinAVR-20080610. Unless you REALLY need to use this positively geriatric version you should upgrade.

 

In this post:

https://www.avrfreaks.net/comment/2004601#comment-2004601

I recommended the easiest route for AVRStudio4 users was to install the final version of Atmel Toolchain that was intended to work with AVRStudio4

 

Atmel AVR 8-bit and 32-bit Toolchain 3.3.1 - Windows
(4921000, updated April 2012)
Windows installer for AVR 8-bit and 32-bit Toolchain version 3.3.2

http://www.atmel.com/System/BaseForm.aspx?target=tcm:26-40855

 

This installer creates registry entries that allow AVRStudio4 to find the toolchain. For a "New Project" it should work straight away, but I don't know whether an existing WinAVR project will. (Probably not actually - Make a new project just in case)

 

-- Nigel

 

 

 

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

This worked for me too under Windows 10 x64.

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

This ALMOST worked for me.  It solved the issue that was claimed it would!  Now I'm on to a new error to work on.  At least its progress.

 

Windows 10 x64, WinAVR 20040404, AVR Studio 4.09.

 

Thanks

 

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

Try the LATEST 1.0.18 DLL, it works on Win10 fine, old ones (including the one in this topic) do not work.

 

Attachment(s): 

Last Edited: Wed. Apr 19, 2017 - 01:50 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Over a year ago, clawson wrote:
But why in 2016 is anyone using WinAVr (last release January 2010).

 

And now we're well into 2017 !!

 

surprise

Top Tips:

  1. How to properly post source code - see: https://www.avrfreaks.net/comment... - also how to properly include images/pictures
  2. "Garbage" characters on a serial terminal are (almost?) invariably due to wrong baud rate - see: https://learn.sparkfun.com/tutorials/serial-communication
  3. Wrong baud rate is usually due to not running at the speed you thought; check by blinking a LED to see if you get the speed you expected
  4. Difference between a crystal, and a crystal oscillatorhttps://www.avrfreaks.net/comment...
  5. When your question is resolved, mark the solution: https://www.avrfreaks.net/comment...
  6. Beginner's "Getting Started" tips: https://www.avrfreaks.net/comment...
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

Thank you. It worked for me on Windows 10.

If you have a qualified firmware which was build with a specific compiler version and you want to achieve comparable binary file, it does make sense to use a specific compiler/toolchain.

In the beginning was the Word, and the Word was with God, and the Word was God.

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

Solved my compilation issue on Windows 10 pro.

was using AVRGCC with programmers notepad.

 

The issue was : 

"main.c:13: fatal error: opening dependency file .dep/main.o.d: No such file or directory"

 

Thanks!

Last Edited: Mon. Sep 11, 2017 - 02:09 PM
  • 1
  • 2
  • 3
  • 4
  • 5
Total votes: 0

sauravshandilya wrote:

sebastor wrote:

I found solution.

Copy this file:

http://www.madwizard.org/downloa...

to utils\bin directory (WinAVR)

 

solved issue for windows-10. 

 

Super agradecido

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

Thank you a lot! It works for Windows 8.1. I have the AVR 4.18 version.

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

Thanks so much , i sol my problem

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

ianuragit wrote:

Solved my compilation issue on Windows 10 pro.

was using AVRGCC with programmers notepad.

 

The issue was : 

"main.c:13: fatal error: opening dependency file .dep/main.o.d: No such file or directory"

 

Thanks!

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

You are a live saver even in 2017.

 

A Big Thank You.

Variety is the spice of live.

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

Works for me, using Windows 10 :)