I already fixed that in my current version of virtualpok, but Janek's patches were created against his version from April.
He already has the new version. I maintain an own linkcmds in virtualpok, as I added a 0x1000 offset to the start of the binary. It confused me to see some strange code in GDB when the actual issue was a NULL pointer. However, this offset led to other issues with debugging pok+rtems, so I am thinking of dropping this again. Meaning, using pc386/startup/linkcmds. Cheers, Philipp On 08/20/2014 04:01 PM, Gedare Bloom wrote: >>>> * Is the linkcmds change required for running pok-rtems? >>> For me, it was required. The old linkcmd script was causing undefined >>> TLS errors while building RTEMS. >> Please report this. This sounds like an independent issue which needs to >> be run down. > I believe this is a known issue. I think Sebastian fixed the in-tree > BSPs, but out-of-tree BSPs also need to add sections for TLS. This > would need to be added to the virtualpok BSP, which is currently > embargoed from entering RTEMS due to needing a binary blob for > libpok.a. > > -Gedare > _______________________________________________ > devel mailing list > devel@rtems.org > http://lists.rtems.org/mailman/listinfo/devel > _______________________________________________ devel mailing list devel@rtems.org http://lists.rtems.org/mailman/listinfo/devel
