On 2017-09-05 15:31, [email protected] wrote: > Hello, > > I tried to use efibootguard on the Siemens IOT2020 but using Mentor > Embedded Linux (instead of Yocto). > I used the meta-efibootguard layer that Andreas kindly posted last week. > > efibootguard was built and shows its prompt but it is then unable to > find a supported watchdog device > (see below for a boot log) > > I eventually traced this problem to be a difference in the compiler output. > The init() function of the driver is expected to be registered in the > .init_array section > > This is definitely the case with GCC 6.3 > It unfortunately isn't with GCC 6.2. > > I checked this by compiling a single line compilation unit: > void __attribute__ ((constructor)) test (void) {} > > readelf shows an .init_array with 6.3 but I get a .ctors section with 6.2
Thanks for analysing. Interestingly, I can reproduce with gcc 4.8.5 of my distro. Neither is init_array empty nor is there a ctors section. Is there some switch that controls this? > > Jan advised me to check here as Andreas may have some hints for me ;) There was also a second issue, and that's where the hints were primarily targeting. Jan -- Siemens AG, Corporate Technology, CT RDA ITP SES-DE Corporate Competence Center Embedded Linux -- You received this message because you are subscribed to the Google Groups "EFI Boot Guard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/efibootguard-dev/fca38757-d1a1-9419-221a-259edc96eb64%40siemens.com. For more options, visit https://groups.google.com/d/optout.
