> Also... Does anybody know how to check for GLIBC versions at compile > time? Is there a version macro or etc that we can check for?
Answering my own question.... It seems we need to test for __GLIBC__ and __GLIBC_MINOR__ and use that to ascertain which signature to use for scandir. That said, I don't know what values map to which implementation... If Pawel or somebody can tell us what values these two macros return on a system that "doesn't work", at least we will know what the changeover value is... I guess that might be enough for us to add a compile-time check to work around this? -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
