[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[avr-gcc-list] Re: AVR-GCC-list Digest, Vol 16, Issue 21

From: Björn Haase
Subject: [avr-gcc-list] Re: AVR-GCC-list Digest, Vol 16, Issue 21
Date: Fri, 26 May 2006 08:49:56 +0200
User-agent: KMail/1.7.1

address@hidden wrote on Freitag, 26. Mai 2006 18:06 :
> Date: Thu, 25 May 2006 21:08:23 -0700 (PDT)
> From: Khusro <address@hidden>
> Subject: Re: [avr-gcc-list] AVR-GCC build failing using MinGW for
>       WinXP
> To: address@hidden
> Message-ID: <address@hidden>
> Content-Type: text/plain; charset=us-ascii
> Hi all,
> I have made considerable progress with everybody's suggestions. I have
> build avr-binutils and avr-gcc
> with the latest atmega2561 patches.  The Last step is avr-libc and I have
> one more hurdle to overcome
> and your help is once again appreciated.
> I have successfully patched the avr-libc sources (which I got from CVS).
> Now I notice that one of the
> patches is for the configure.ac file. This means that I have to create the
> configure script using autoconf.
> I hope all is correct till now? Well, herein lies the problem. I of course
> downloaded autconf for windows
> and installed it, along with M4 for windows as well. When I do autoconf
> configure.ac I get the following


I'm not an expert concerning the avr-libc build system, but IIUC, you should 
run the bootstrap script rather than excecuting autoconf yourself. Hopefully 
this solves your problem.

Fabrizio Tironi found out that I forgot to attach the two header files for the 
atmega256x in the avr-libc patch. 

Aesok already has prepared them and you could download them at


. They need to go into the "include/avr" directory of avr-libc.

Here you also will find an additional patch. I found one place within avr-libc 
where the code pops 2 bytes from the stack in order to simulate the effect of 
two "ret" instructions simultaneously. For avr6 we need to pop 3 bytes. The 
patch affects the file



Attachment: avr_libc_libm_error_return.patch
Description: Text Data

reply via email to

[Prev in Thread] Current Thread [Next in Thread]