> According to STR #2205 (for FLTK 2.0) this is a change in > glibc, please > see the note from jue at 07:09 Jun 17, 2009 and the links in [1]. > > "So the only clean solution for fltk is either have a #if > GLIBC in the > sources-files or some additions to the autoconf stuff." > > There's also a workaround described, but IMHO we need to > check this for > all FLTK versions ASAP. > > Anybody who feels fit to do this with autoconf / configure ?
That doesn't sound like a job for me, then... Very much *not* my strong suit. That said, detecting this in autoconf does sound like it would be the best bet. I would guess that, if we can detect the correct case, we already have the necessary pieces in place, so that scandir either gets the "old" signature or the "HP_UX" signature and all will work... Looking at the STR's referenced, #2205 and #2202, I'd say that the fix proposed in #2202 is just plain wrong, in that it might fix the problem for systems with glibc >= 2.10 but will break it for everyone else. That leaves us with either detecting this during configure, or with somehow checking the version of GLIBC at compile time and selecting accordingly. That might actually be straightforward and reasonably robust...? Anybody? -- 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
