Sree Harsha Konduri wrote:
../../../../../pc386/lib/librtemsbsp.a(ckinit.o): In function `bsp_clock_nanoseconds_since_last_tick_i8254': /home/harsha/rtems/4.11/pc386/i386-rtems4.11/c/pc386/lib/libbsp/i386/pc386/../../../../../../../../rtems/c/src/lib/libbsp/i386/pc386/clock/ckinit.c:153: undefined reference to `Clock_driver_isrs'
The clock driver in the pc looks suspect. The clockdrv_shell.h code in the bsp/shared area uses CLOCK_DRIVER_ISRS_PER_TICK as a 0 or 1 to determine if it is enabled or disabled while this clock driver seems to do something different with the same label. It also has a bug where the data is conditional while the code expects it to be present. I do not understand the logic being used here. Someone who knows this driver will need to comment and look at a fix.
The fix I pushed to the clockdrv_shell.h's use of CLOCK_DRIVER_ISRS_PER_TICK is correct and RTEMS's use of defining 0 and 1 to things via BSPOPTS then using '#ifdef' is broken. All BSPOPT defines need to be '#if ....'.
Chris _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
