Why does this tool need both shared libraries and header files to check ABI compliance?
- Im using header files which accompany two different third-party libraries, and they are ``helpfully\ defining common macros such as TRUE, FALSE, Min(), and Max(), but the definitions clash with each other and with definitions Id already established in my own header files. What can I do?
- When I compile software that uses a configure script, the configure script thinks my system has all of the header files and libraries it is testing for. How do I get configure to work correctly?
- Where are binary programs, header files, and load libraries installed?