As mentioned elsewhere, the UDI Reference Implementation is a non-trivial hunk of code that interfaces with deep, dark corners of a number of operating systems and a wide variety of host and add-in hardware. It also serves several potential audiences.
This page is a compendium of known issues and quirks that you may encounter when working with the reference implementation. If you are having trouble working with your copy of the reference implementation, check this page to see if the answer lies here.
If your problem doesn't appear here, check the bugs list for Project UDI to see if the problem has already been reported. If it has, you might want to supplement the problem report if you have additional useful information.
If your problem is does not appear in the buglist and is unique, you now have two choices:
"make CC=foo_cc") don't seem to be applied to the subsequent build operation.
udibuild)and a driver description file (the Static Properties file, usually
udiprops.txt) which perform the necessary functions to build the driver. The source code dependencies are noted in the Static Properties (assuming this is a source code distribution) and the
udibuilduses the information in this file to invoke the proper compile and link operations on your system.
udibuildtool usually knows what's best, it doesn't use any of the standard environment variables or command-line overrides. If you find yourself wanting to do this, think and then think again about why you need this; it might be that you are introducing environment dependencies into your otherwise portable UDI module.
"udibuild -h") should cause them to output helpful usage information.
# UDI_CC=foo_cc; export UDI_CC
# make UDI_CC=foo_cc
udibuild. Therefore, you should also use the normal command line overrides as well (e.g.
udibuildutility, and the format and content of the Static Properties file for a UDI module. UDI does NOT specify the flags, environment overrides, or other utilization of the
udibuildutility, other than to say that simply typing
udibuildin the directory that contains the driver and the Static Properties file should be sufficient to build the module in most situations. This means that the overrides you use in one development environment may not apply in another development environment.
envcommon/udi_mei.c:559:25: unterminated argument list for macro "_UDI_VA_ARGS_0"
udibuild: ERROR: `cc' command failed (1).
# ln -s `which kgcc` /usr/local/bin/cc
# chmod +x /usr/local/bin/cc
# CC=kgcc; export CC
# UDI_CC=kgcc; export CC
posix_initoperations, you have a version of GDB that doesn't support Linux threads very well (e.g. the GDB shipped with RH7.0).
File last modified: 00:00 Thu January 1, 1970