2013/9/8 Riccardo Mottola <[email protected]>: > Hi, > > > On 09/07/13 17:57, Maciej (Matchek) Bliziński wrote: >> >> 2013/9/7 Riccardo Mottola <[email protected]> >>> >>> Are there reliable #ifdef's for identifying solaris? and then, in case, >>> its versions? I need certain workaround for solaris and, furthermore some >>> are needed only for solaris 8/9, but no longer in 10+. (I'm struggling with >>> the missing stdint.h and the incomplete inttypes.h) >> >> Why not have a ./configure test for the exact feature or bug you're >> interested in detecting, and an own #define? > > First, not everything is easy to check, also these tests need to work on > non-solaris platforms. Perhaps you do have some ready tests? > The first problem is checking for stdint.h: that's easy, the alternative is > inttypes. But then checking for various macros, some of those are defined > "blank" on solaris 8/9, not just undefined. (MIN/MAX limits, PRTuPTR and > that kind of stuff).
If you could describe here an example of a test that doesn't look easy, maybe someone would chime in with a hint. Is your code available to be viewed? If not, can you post a snippet that breaks? > Furthermore, configure is easy for a program, but more difficult to use for > a library, a Framework where you install headers, because you don't install > config.h, or at least so I understand it. It's possible. You do install config.h, giving it either a unique name such as project-config.h or putting it into a project-specific directory. http://www.openismus.com/documents/linux/building_libraries/building_libraries#installingheaders http://stackoverflow.com/questions/1810216/autoconf-where-does-config-h-go which links to: http://www.gnu.org/software/autoconf-archive/ax_prefix_config_h.html > So if you have some solaris ifdef's I would still a appreciate :) There must > be! Perhaps a mix of the two tings will eventually help me better. No, this is a wrong way of doing this. All you need is to learn how to write tests and use the results. Maciej _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
