On Fri, 7 May 2021, Alin Marin Elena wrote:
Hi,
so a workaround was to pass this to the linker -Wl,--build-id=none personally I understand little on the side effects of this so I do no know if that can be some default setting in the linker. but with that flag the size is the same as stm32 toolchain.
That's quite unbelievable ... if you can reproduce this and share the linker input files it's worth reporting a bug for. Please provide the output of the linker gcc command with -v appended as well. Richard.
Regards, Alin
Regards, Alin
Without Questions there are no Answers! ______________________________________________________________________ Dr. Alin Marin ELENA http://alin.elena.space/ ______________________________________________________________________
On Fri, 7 May 2021 at 12:35, Stefan Brüns <stefan.bruens@rwth-aachen.de> wrote:
On Freitag, 7. Mai 2021 08:07:18 CEST you wrote:
Hi Stefan,
I got the rpm and installed now seems to work, in the sense I do not get a linker error anymore... however the size of the binary produces is crazy big .rwxr-xr-x 1 134M drFaustroll users 7 May 06:54 -I m65_rev1_uk.bin vs .rwxr-xr-x 1 30k drFaustroll users 7 May 07:05 -I m65_rev1_uk.bin by using the stm32 toolchain..
now since the hex files produced are more or less the same 30K I suspect the issue may be more complex and maybe related to the other bug.
I suspect an incomplete/insufficient linker script, including too much in the binary.
Have a look at the size of the sections in the corresponding elf files: $> objdump -h m65_re1_uk.elf
If in doubt, post the results on the list.
Kind regards,
Stefan
-- Stefan Brüns / Bergstraße 21 / 52062 Aachen home: +49 241 53809034 mobile: +49 151 50412019
-- Richard Biener <rguenther@suse.de> SUSE Software Solutions Germany GmbH, Maxfeldstrasse 5, 90409 Nuernberg, Germany; GF: Felix Imendörffer; HRB 36809 (AG Nuernberg)