Re: [U-Boot-Users] [PATCH 1/6] AVR32: Use -g instead of -gstab s in AFLAGS_DEBUG
This patch replaces -gstabs with -g when compiling for AVR32, so that the default debugging format is used. Ulf Samuelsson reported problems on ARM when changing this unconditionally, so this patch has been updated to only change AVR32.
Oops. I missed this.
Previous identical patch already applied.
Not 100% identical...this one only makes a difference on AVR32, while the other one changes everyone to use -g. Ulf reported build problems on ARM with the other patch, so I made it conditional.
Sure you don't want this patch instead of the other one?
I'm not sure. Which sort of problems was this exactly? >Whic boards /
platforms, and which toolchains?
Crosstool-0.42 generic-arm gcc-3.4.6-softfloat binutils 2.16.1 glibc-2.3.5 (IIRC)
Refused to compile when -gstabs was changed to -g board=at91rm9200df which is a pure dataflash version of at91rm9200dk and is not part of the main tree. I believe that at91rm9200dk should exhibit the same problem
Best regards,
Wolfgang Denk
Best Regards, Ulf Samuelsson ulf@atmel.com +46706224457
Dear Ulf,
in message crmSxxCQKzD6.801NTpXz@mailout.dof.se you wrote:
I'm not sure. Which sort of problems was this exactly? >Whic boards /
platforms, and which toolchains?
Crosstool-0.42 generic-arm gcc-3.4.6-softfloat binutils 2.16.1 glibc-2.3.5 (IIRC)
Refused to compile when -gstabs was changed to -g
Can this toolchain compile any source file using somthing like this:
${CROSS_COMPILE}gcc -g -c foo.c
?
If this is the same problem as previously reported by Matthew, I tend to blame it on the toolchain...
Best regards,
Wolfgang Denk
Dear Ulf,
in message crmSxxCQKzD6.801NTpXz@mailout.dof.se you wrote:
I'm not sure. Which sort of problems was this exactly? >Whic boards /
platforms, and which toolchains?
Crosstool-0.42 generic-arm gcc-3.4.6-softfloat binutils 2.16.1 glibc-2.3.5 (IIRC)
Refused to compile when -gstabs was changed to -g
Can this toolchain compile any source file using somthing like this:
${CROSS_COMPILE}gcc -g -c foo.c
?
Yes, it is only when the gcc driver calls the assembler that the AFLAGS gets used and the arm assembler apparently requires that you qualify "-g" with "stabs" .
Maybe a better idea for patch is to override "stabs"
pseudo code:
if ! defined(DEBUG_FORMAT) DEBUG_FORMAT=stabs end if
AFLAGS="-w,g$(DEBUG_FORMAT)"
If this is the same problem as previously reported by Matthew, I tend to blame it on the toolchain...
Best Regards Ulf Samuelsson
participants (3)
-
Ulf Samuelsson -
Ulf Samuelsson -
Wolfgang Denk