Modules were being linked with the GCC library (-lgcc) which meant a copy of some library code was being included in every module. This has been removed and the modules now use the GCC library code from the core CHDK.Required inclusion of the '__gnu_thumb1_case_uqi' and '__gnu_thumb1_case_uhi' functions in the module build as these are always called using short calls, so can't be linked from the module to core. Added in the, previously unused, libc library so they are only included when needed by each module.
elf2flt unknown symbol: '__gnu_thumb1_case_shi'
Quote from: philmoz on 21 / November / 2013, 21:07:51Modules were being linked with the GCC library (-lgcc) which meant a copy of some library code was being included in every module. This has been removed and the modules now use the GCC library code from the core CHDK.Required inclusion of the '__gnu_thumb1_case_uqi' and '__gnu_thumb1_case_uhi' functions in the module build as these are always called using short calls, so can't be linked from the module to core. Added in the, previously unused, libc library so they are only included when needed by each module.I'm gettingCode: [Select]elf2flt unknown symbol: '__gnu_thumb1_case_shi'when compiling one of my modules. I must be doing something none of the official modules do. Any idea what this function is? Some kind of signed half integer operation?
The __gnu_thumb1_case_??? instructions are used to implement a 'switch' statement in the C code.If you modify the modules/Makefile you can generate the dump files for each module.Do this with your module in version 1.2, and then you can cut and paste the source for __gnu_thumb1_case_shi into the thumb1_case.S file (lib/libc).Alternatively put the affected switch code somewhere in the core C code and copy the result from the main.bin.dump output.
In case I'd like to try adapting some third party code into a module, would it be possible to build selected modules the old way (in order to avoid adding previously-not-encountered libgcc functions to the export list)?
Quote from: srsa_4c on 26 / December / 2013, 18:24:42In case I'd like to try adapting some third party code into a module, would it be possible to build selected modules the old way (in order to avoid adding previously-not-encountered libgcc functions to the export list)?Is this possible somehow?
You would need to create a custom target in the makefile that included '-lgcc' in the link options.If you copy the generic %.flt target to a mymodule.flt target and add -lgcc after $(LDLIBS) it might work.
Related to http://chdk.setepontos.com/index.php?topic=10617.msg108560#msg108560In trunk changeset 3294 I modified PAUSE_FOR_FILE_COUNTER to only pause if the new counter isn't the previous counter + 1, or is unknown.I used +1 rather than checking if they are equal because there are potentially cases where the last_fc value might not be up to date.I think this is OK, but verification on other PAUSE_FOR_FILE_COUNTER cameras would be appreciated.
Started by Mac General Help and Assistance on using CHDK stable releases
Started by CoffeeGrip General Help and Assistance on using CHDK stable releases
Started by DavidB « 1 2 » Hello, I'm a NEWBIE - HELP!! (Newbies assistance, User Guides and thank you notes)
Started by Pseudothink Creative Uses of CHDK
Started by bitterlake Script Writing
