This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug c/47384] New: Doesn't indicate failure status when it doesn't support (attiny2313A)
- From: "choudary.omar at gmail dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Thu, 20 Jan 2011 20:08:20 +0000
- Subject: [Bug c/47384] New: Doesn't indicate failure status when it doesn't support (attiny2313A)
- Auto-submitted: auto-generated
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47384
Summary: Doesn't indicate failure status when it doesn't
support (attiny2313A)
Product: gcc
Version: 4.5.2
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: c
AssignedTo: unassigned@gcc.gnu.org
ReportedBy: choudary.omar@gmail.com
Created attachment 23049
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23049
Patch to correct the bug
This is a bug unresolved from the previous version 4.5.1:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45261
>From the original description:
---------------------------------------------------------------
When configuration script of avr-libc tries to check if gcc has support for
Attiny2313A it doesn't indicate any failure even if it really doesn't support
it. I found about that trying to build avr toolchain using this version of gcc.
Here is a part of config.log:
configure:5374: checking if avr-gcc has support for attiny2313a
configure:5390: avr-gcc -c -mmcu=attiny2313a conftest.c >&5
unknown MCU 'attiny2313a' specified
...
configure:5397: $? = 0
configure:5416: result: yes (which should indicate NO)
this bug doesn't allow to build avr-libc-1.7.0 because it doesn't let 'make' to
build the code.
---------------------------------------------------------------
I had to attach a modified patch that patches version 4.5.2 instead of 4.5.1.