> 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?
Can somebody with a failing F11 (or similar) system compile and run the
following code and let us know what the output is, please?
----------------
#include <stdlib.h>
#include <stdio.h>
int main(void)
{
#ifndef __GLIBC__
printf("No GLIBC macro detected\n");
#else
printf("__GLIBC__ defined as: %ldL\n", (long) __GLIBC__);
# ifdef __GLIBC_MINOR__
printf("__GLIBC_MINOR__ defined as: %ldL\n", (long) __GLIBC_MINOR__);
# endif
#endif
#ifdef __GLIBCPP__
printf("__GLIBCPP__ defined as: %ldL\n", (long) __GLIBCPP__);
#endif
#ifdef __GLIBCXX__
printf("__GLIBCXX__ defined as: %ldL\n", (long) __GLIBCXX__);
#endif
return 0;
}
/* end of file */
----------------
--
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
