RTOS/OMAP-L138: How to get rid of Path/Date/Time info in the Binaries for Configuration Management issues?

Part Number:OMAP-L138

Tool/software:TI-RTOS

We noticed that the Binaries contain Path/File/Time information in the binaries.  This is very bad for Configuration Management issues.  Need to be able to rebuild on different machines in different time zones years later and get an exact matching binary.

We think we traced it down to calls like this:

Log_error0("osu_util_copy_general_data_to_msg_p: Bad passed in pointer!");

And maybe this:

Log_info0("Suspending Tasks!!!)");

Error_raise(NULL, Error_E_generic,  (IArg) "Unable to post message to queue 0x%x on ARM.\n",  (IArg) msg_struct_p->msgq.id);

Is there anything in the CFG files we can do to trim this information or maybe during a release build make it a null call?

Are there other calls that will append information that will cause use to have different Binaries if we build on a different machine or date/time?

Thanks