DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2313 Version: 2.0-current Okay, meanwhile I can say that both solutions (yours and mine) are not correct. The first warning you posted: "configure: WARNING: Not using SunOS scandir emulation function." makes the difference. This warning is in the configure script since Feb. 18, 1999 and should disable the use of Solaris's scandir() function (svn releases #289 and #294). Subversion log: ------------------------------------------------------------------------ r289 | mike | 1999-02-18 14:42:08 +0100 (Thu, 18 Feb 1999) | 6 lines Updated scandir() check to use FLTK scandir function instead of Sun scandir(). [...] r294 | mike | 1999-02-18 16:05:50 +0100 (Thu, 18 Feb 1999) | 3 lines Updated Solaris scandir() check [...] ------------------------------------------------------------------------ I don't know *why* this has been done, and I don't know if this is still necessary. Anyway, if we leave it this way, then we should also disable HAVE_SCANDIR_POSIX for Solaris. Otherwise we should remove the special case completely. Mike, if you read this, can you enlighten us what should be done? Enable Solaris scandir() or disable it? The previous decision is almost 11 years old. FWIW: There is also potential trouble with FLTK 1.1 and 1.3, but this is slightly another case, because scandir() is also replaced with fl_scandir() there). Link: http://www.fltk.org/str.php?L2313 Version: 2.0-current _______________________________________________ fltk-bugs mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-bugs
