not compiling under new gcc about bitlash HOT 9 CLOSED

Thanks for the bug report, and the diff.

What version of gcc causes the issue? I would like to be able to reproduce the problem to be sure I've fixed it.

Thanks,

-br

from bitlash.

gcc version 4.6.3 20120306 (Red Hat 4.6.3-2) (GCC)
this problem started on 4.6.1 if I'm not mistaken.

from bitlash.

Thanks for the update. I'm puzzled how you built that setup - are you compiling through the Arduino IDE with an updated AVR toolset, or are you using a command-line technique with a makefile, maybe? Any help in reproducing your environment would be appreciated. (If I'm looking at the right binary, avr-gcc 4.5.3 is what ships with arduino 1.0)

from bitlash.

Sorry for the lack of information.
I'm using Fedora 16 - linux. For linux the IDE doesn' t comes with its own compiler. Instead it uses the system's builtin GCC, having this version I gave you. Indeed, when using the version for windows I don't have any problem compiling.
Nevertheless, assuming that the version for windows will one day be updated, you will encounter this problem soon or late in a future update.

from bitlash.

I built a fedora 16 virtual box vm here and I can reproduce the compile problem. Thanks.

I have a configuration issue you might be able to help with. When I run the arduino executable, it complains "WARNING: RXTX Version Mismatch \n jar version: RXTX-2.2 \n native lib Version = RXTX-2.2pre2." Any thoughts on mending it?

Perhaps as a consequence, the serial port menu is grayed out. Is it necessary on Fedora to install a driver for the FTDI interface?

Any thoughts would be helpful. I'd like to be able to reproduce that spurious character bug if possible, and to do that I need to be able to upload to the Arduino...

from bitlash.

An update. The FTDI virtual serial port is properly created at /dev/ttyUSB0, and I can use screen to talk to an arduino programmed from OS X with the older avr-gcc. Back to the RXTX version issue I suppose.

from bitlash.

you have to add the user to the groups:
lock and uucp

and run as root (at every boot):
chown root.lock /var/lock/
chmod g+rw /var/lock/

The problem is that you cant get the file lock on the socket.

from bitlash.

Thanks, it works, I never would have guessed.

from bitlash.

Please try commit 5cfc04b. It compiles under Fedora 16. I was able to reproduce issue 2 (spews lunch on error) and correct it, at least for the moment, by disabling the error traceback. So issue 2 should be addressed as well.

Please let me know how it works for you.

from bitlash.