> Maybe there is a problem with his toolchain then? > It sounds (based on the version in Duncan's post) as if he has an older > Centos but a newer gcc than Duncan has, so things may have been updated > from standard - I wonder if there's some OS / gcc / binutils mismatch or > something that might cause this? Just wondering...
[At work, on the CentOS 5.6 system with gcc 4.1.2...] We use a commercial application that generates fortran code that then has to be linked against their supplied libraries. We discovered that the differences between gcc 4.1 and different versions of 4.2 gave us a lot of grief. Up until then we had assumed that using a newer version would be OK. Since then we always install the specific version of gcc needed to match the libraries in some out of the way directory off the main PATH and change the applications scripts to compile against that. Apart from me building fltk versions in my own scratch area, we tend to stick with just the official CentOS updates and patches because it Just Makes Life Simpler (tm :-) Having said that, CentOS 5.6 is well behind the curve these days, and when the commercial app was built on a 64-bit OpenSuse 11 system, we ended up with all sorts of probs, and they had to go back to a VM with OpenSuse 10.1 installed to rebuild for us and RedHat-5 customers... :-( We are so glad that CentOS 6 is finally out so we can catch up a bit. D. _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
