-Original Message-
From: Paulo Marques [mailto:[EMAIL PROTECTED]
Sent: Saturday, February 16, 2008 5:20 PM
To: Weddington, Eric
Cc: avr-gcc-list@nongnu.org
Subject: Re: [avr-gcc-list] GCC 4.3 20080215 snapshot broken for AVR
Quoting Weddington, Eric [EMAIL PROTECTED]:
Hi All,
Hi, Eric
I just filed GCC bug report #35218:
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35218
GCC 4.3 20080215 snapshot is broken for the AVR. Last
week's snapshot
20080208 built fine for the AVR. The issue seems to be in
building the
documentation, nothing AVR specific.
I've just updated to GCC 4.3.0 20080216 and built it just fine. So,
either this is some problem with some other tools (texi2dvi
or texi2pdf
or something), or it is already fixed in the current version...
Thanks for checking. Joerg Wunsch also confirmed with an updated
repostitory. Can you also please check the *snapshot* too? I'd like to
know wether the snapshot itself is broken (and now fixed in mainline),
or whether it's possibly my tools.
This is important as the GCC folks are planning a 4.3.0 release
candidate on Monday. The AVR port is neither a primary or
secondary
platform (at this time) which means that the GCC project is
free to do
release whether the AVR port is broken or not.
I'm starting to get a little put down by the lack of response
from the
gcc community. I've already reported about 6 bugs, and
proposed patches
to fix 4 of them. Up till now, they didn't even update the
state of the
bugs, nor did they apply any of the patches.
Am I barking at the wrong door here? Should I start posting on
[EMAIL PROTECTED] to get more feedback?
*sigh*
This gets slightly complicated. The best thing to do is to follow their
procedures:
- post the patch to the matching bug report
- post the patch to gcc-patches mailing list. CC the AVR port
maintainers (Anatoly, Denis). I wouldn't mind being CCed too.
The patches should be tested to ensure no new regression test failures,
and should also include the relevant ChangeLog entries. You should
already have an FSF Copyright Assignment paperwork on file.
- Wait for a maintainer to approve the patch. If you haven't heard
something in a week, ping it on the list. Keep pinging until approved
and committed, or patch was rejected for whatever reason, then fix the
patch and repeat.
Part of the problem is that Denis is not very active on the AVR port, so
it's just currently Anatoly. I'm working on getting FSF Copyright
Assignment paperwork done, so I can be more of a help in this area.
But I can tell you that it *definitely* helps to put together a working
patch and post it on the matching bug report. Then at least everything
is *saved* and at least the patches can be rolled into the distros until
such time as it gets committed in the upstream projects.
HTH,
Eric Weddington
___
AVR-GCC-list mailing list
AVR-GCC-list@nongnu.org
http://lists.nongnu.org/mailman/listinfo/avr-gcc-list
