As Ed wrote:
> I sorry to be such a pain but, here are two more problems with the
> last patch file called: "avarice-2.10_atxmega256a3_support.patch".
Given my explanation about the current deficiencies of Xmega
debugging, are you sure you even *want* to apply that patch
at all?
> It seems that
Hi again:
I sorry to be such a pain but, here are two more problems with the
last patch file called: "avarice-2.10_atxmega256a3_support.patch".
Problem #1:
All the file names in this patch are prefixed by "+++
avarice-2.10_patched/src/".
The only way to get this patch to work is by rem
Hi Ed,
Well, I would think that we need to take a look at the usage of the
default_target variable. Is it really used as a variable, i.e., is it
reassigned another value elsewhere in the program? If not, then I would think
that it would be safe to say that it can be declared a "const char *", a
All:
Here is another problem with the bundle of Avarice patches, this patch
"warnings.patch" has a problem at line 198 of the patch file. The
patch process barfs on hunk #3 with an error: (Hunk #3 FAILED at 244.
1 out of 3 hunks FAILED -- saving rejects to file src/
jtag2prog.cc.rej). It app
As Ed wrote:
> I also have another patch listed by the people on AVR freaks which is
> from "Debian" for Avarice called: FTBFS: jtag2usb.cc:98: error:
> invalid conversion from 'const char*' to 'char*'
> the file is called "avarice_210.patch".
This has already been fixed in the CVS version, s
