[Top][All Lists]

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

Re: [avr-libc-dev] [bugs #10329] crtm168.o is not being built

From: E. Weddington
Subject: Re: [avr-libc-dev] [bugs #10329] crtm168.o is not being built
Date: Thu, 07 Oct 2004 11:45:44 -0600
User-agent: Mozilla Thunderbird 0.7.3 (Windows/20040803)

Theodore A. Roth wrote:

On Thu, 7 Oct 2004, E. Weddington wrote:

What you are seeing is correct and will happen on all systems, not just
cygwin. It's a side effect of the multi-lib build method. It's also
something I've always detested and would like to see go away, but the ML
part of configure is so complicated, even I don't understand all of how
it works (which is why I did the complete rewrite on the autoconf

Forgive my memory loss, but is the autoconf branch before 1.0.4 release?
or will it be sometime after? What's the relationship?

It's a branch off of head which builds a crt*.o file for every supported
device instead of only for avr2, avr3, avr4, and avr5. It remains an
experimental branch until some changes are made in gcc/binutils (which
may never happen).

Ah, that one. Why do you think this may never happen (changes in gcc/binutils)?

IMO, this feature will be sorely needed as
1. There are more than one device now that won't have working eeprom routines because of the current architecture and non-standard locations of these registers.
2. There are more new devices that are coming up from Atmel.


reply via email to

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