anilgkts / arduino

Automatically exported from code.google.com/p/arduino
Other
0 stars 0 forks source link

error: attempt to use poisoned "SIG_USART0_RECV" #955

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Compile any sketch (.ino). I tested with Blink example.

What is the expected output? What do you see instead?
The compilation ends with error.

/usr/bin/avr-g++ -c -mmcu=atmega2560 -DF_CPU=16000000L -DARDUINO=100 -I. 
-I/usr/share/arduino/hardware/arduino/cores/arduino 
-I/usr/share/arduino/hardware/arduino/variants/mega   -g -Os -w -Wall 
-ffunction-sections -fdata-sections -fno-exceptions 
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp -o 
build-cli/HardwareSerial.o
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp:91:41: 
error: attempt to use poisoned "SIG_USART0_RECV"
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp:101:15: 
error: attempt to use poisoned "SIG_USART0_RECV"
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp:132:15: 
error: attempt to use poisoned "SIG_USART1_RECV"
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp:145:15: 
error: attempt to use poisoned "SIG_USART2_RECV"
/usr/share/arduino/hardware/arduino/cores/arduino/HardwareSerial.cpp:158:15: 
error: attempt to use poisoned "SIG_USART3_RECV"
make: *** [build-cli/HardwareSerial.o] Error 1

What version of the Arduino software are you using? On what operating
system?  Which Arduino board are you using?

OS: Debian GNU/Linux unstable.

Packages:
avr-libc 1:1.8.0-2
avrdude 5.11.1-1
binutils-avr 2.20.1-2
gcc-avr 1:4.7.0-2
arduino 1:1.0.1+dfsg-2
arduino-core 1:1.0.1+dfsg-2                   
arduino-mk 0.8-4

Board: Mega2560             

Please provide any additional information below.

Original issue reported on code.google.com by dieg...@gmail.com on 10 Jun 2012 at 4:26

GoogleCodeExporter commented 9 years ago
Downgrading to gcc-avr 4.3.5 (from Debian stable) solves the problem.

Original comment by dieg...@gmail.com on 10 Jun 2012 at 4:46

GoogleCodeExporter commented 9 years ago
What should these signal names be replaced with?  What versions of avr-gcc / 
avr-libc do those replacements work with?

Original comment by dmel...@gmail.com on 17 Jul 2012 at 3:32

GoogleCodeExporter commented 9 years ago
In more recent avr-libc implementations, the SIGNAL macro and concept is 
replaced by the ISR macro, and the SIG_xxxx names replaced by xxxy_vect values. 
 (presumably, to avoid conflicts with posix-style signals.)  The current 
Arduino code is actually quite a mix, using SIGNAL some places, ISR in others, 
and using xxxy_vect isr names with the SIGNAL macro...

Attached are diffs (from current sources) that should fix this.
Compiles of ASCIITable on Mac yield identical binaries with and without this 
patch; I haven't actually tested with newer compilers.

Original comment by wes...@gmail.com on 30 Aug 2012 at 12:51

Attachments:

GoogleCodeExporter commented 9 years ago
Attached is a patch from the 1.0.1 release that should fix this. Code builds 
properly with avr-libc 1.8.0, avr-gcc 4.7.2 and avr-binutils 2.22. It now 
depends on avr-libc>=1.4.0.

However, I have not verified that the binaries are correct--I have no reason to 
believe that they aren't, but I haven't verified it.

Original comment by luke.t.s...@gmail.com on 21 Oct 2012 at 1:33

Attachments:

GoogleCodeExporter commented 9 years ago
That is to say that Bill Westfield's patch (comment 3) does NOT actually build 
with a new avr-libc.

Original comment by luke.t.s...@gmail.com on 21 Oct 2012 at 1:37

GoogleCodeExporter commented 9 years ago
Fixed, it will be available on next releases (1.0.5 and 1.5.3)

Thanks for your patches.

Original comment by c.mag...@arduino.cc on 3 Apr 2013 at 11:57

GoogleCodeExporter commented 9 years ago
[deleted comment]
GoogleCodeExporter commented 9 years ago
patch from comment #4 works like a charm.
needed it for patching sanguino core (644 port).
thank you!

Original comment by kau...@gmail.com on 3 Jul 2014 at 10:56

GoogleCodeExporter commented 9 years ago
after downloading this sig-patch.diff file where should it be placed or what 
should be done with it?

Original comment by aguiar.l...@gmail.com on 8 Apr 2015 at 5:32