>>>>> Joerg Wunsch <j...@uriah.heep.sax.de> writes: >>>>> As Ivan Shmakov wrote:
>> I've just tried to build a program for ATtiny13A on a recent >> Debian Wheezy, and got: >> $ avr-gcc -g -O2 -Wall -pedantic -std=gnu99 -mmcu=attiny13a \ >> -L/usr/lib/avr/lib/avr25 ../6pp5iouyw6unnen7egfroozp8b.c \ >> -o 6pp5iouyw6unnen7egfroozp8b >> /usr/lib/gcc/avr/4.7.0/../../../avr/bin/ld: crttn13a.o: No such file: No >> such file or directory >> collect2: error: ld returned 1 exit status > Johann, is this the symptom for bug 35407? > https://savannah.nongnu.org/bugs/?35407 I don't seem to understand how it could be related. Is there a specific test I can run? FTR, as of 1:1.8.0-3, Debian's avr-libc ships both lib/crttn13.o /and/ lib/avr25/crttn13.o (for the similar, ATtiny13 MCU), differing in only a dozen of bytes. > Ivan, do you have a random generator for the names of your source > file? :-) Well, I grow tired of naming my throw-away code test-1.c, …, test-510.c, etc. Given that I've used to write code on several hosts, using a randomly-generated filename (or, alternatively, one that's based on a timestamp) helps a lot when copying the files between hosts. (I'd prefer a filename based on a digest, or a tree hash, of the file's contents, but it'd be a real hassle given the tools I'm currently relying upon.) Specifically, 6pp5iouyw6unnen7egfroozp8b is a zBase32-encoded [*] UUID (e. g., [1]), based on a random number. [1] urn:ietf:rfc:4122 http://tools.ietf.org/html/rfc4122 [*] The standard form would be: beb55de1-04d4-4f21-90e8-c81402e16d27. -- FSF associate member #7257 _______________________________________________ AVR-libc-dev mailing list AVR-libc-dev@nongnu.org https://lists.nongnu.org/mailman/listinfo/avr-libc-dev
