> > I wonder if when you checked out the new fltk2, did you also > do a 'make install' after doing the 'make' to install it?
I am pretty sure that I executed "make install" after "make" the new version (r6829) fltk2 lib. Besides, before r6829 was installed, the above g++ command was already faulty in previous r67xx. After then, I installed r6829. So, I think it should not because missing "make install". > > > If not, the 'old' fltk2 would still be out there in > /usr/local/include, > which would link against the 'old' fltk2, > while the 'new' fltk2 would still be in your fltk-2.x dir. > > The above g++ command assumes linking against the 'installed' fltk2, > where 'fltk2-config' will use the libs that are in the fltk2 source > directory (which would work whether you did the 'make install' or > not) > > This could explain why there's a difference between using > fltk2-config > and the g++ command. > > I would think if you do a 'make install', then the above "g++" > command > would then work normally. > > If that helps, then the issue was the 'old' fltk2 that you had > installed was the problem. > _______________________________________________ > fltk-dev mailing list > [email protected] > http://lists.easysw.com/mailman/listinfo/fltk-dev >
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
