Re: [fltk.bugs] [LOW] STR #2555: configure looks for native ar, not target one (crosscompiling)
[STR Closed w/Resolution] Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Fix Version: 1.3.0 (r8397) Added fix version (8397). Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Fix Version: 1.3.0 (r8397) ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [LOW] STR #2555: configure looks for native ar, not target one (crosscompiling)
[STR Closed w/Resolution] Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Fix Version: 1.3.0 Fixed in Subversion repository. ... and closed. Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Fix Version: 1.3.0 ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
Re: [fltk.bugs] [LOW] STR #2555: configure looks for native ar, not target one (crosscompiling)
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR Active] Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Thanks for pointing this out. It was a problem when cross-compiling on Cygwin with the MinGW-w64 compiler to generate 64-bit executables. We already had a fix (hack) for windres, but AC_PATH_TOOL seems to be the missing link. I didn't know that (still learning autoconf). Looking into it and testing right now... Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs
[fltk.bugs] [LOW] STR #2555: configure looks for native ar, not target one (crosscompiling)
DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW. [STR New] Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current Since ar messes with symbols, you should use one that understands the target system. Hence configure.in should look for it using AC_PATH_TOOL, not AC_PATH_PROG. For libfltk.a we seem to run the proper ranlib right after, so it's probably not a practical issue right now. Still, it could be misused in the future so it's probably best to fix it at the source. Link: http://www.fltk.org/str.php?L2555 Version: 1.3-current ___ fltk-bugs mailing list fltk-bugs@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-bugs