nilan wrote: >> nilan wrote: >>>>> 2)As you told i installed fltk 1.3.0 and unmerge previous=20 >>>>> 1.1.7 and then >>>>> compiled my program. it was ok up to compile. >>>> One possibility is that you have managed to create a build that is a >>>> hybrid of 1.1.7 and 1.3.x. This might be possible since the header files >>>> largely match, but the underlying ABI does not. So, if you built your >>>> 1.3.x version, but it picked up bits of a pre-existing 1.1.7 >>>> installation, bad things might happen... >>>> >>>> I would suggest you remove all traces of any previous 1.1.7 or 1.3.x >>>> install, then re-install 1.3.x from clean baseline, then clean and >>>> remake all your code, and see how you get on. >>>> >>>> If you are running multiple versions of fltk in parallel, you do need to >>>> be careful about cross-pollution between them. (It is perfectly >>>> possible, I have 5 variants on this box, but you do need to be careful!) >>>> >>>> >>> I have already checked it and did install after cleaning every things >>> regarding previous installation but problem didnt solve. >> I also think that Ian's assumption is the most probable. Maybe you're >> linking dynamically with an old shared fltk .so file. >> >> Please cd to your 1.3 root dir and enter >> >> ldd fluid/fluid >> >> and post the output here. You should look at anything related to fltk >> and check if there is a FLTK 1.1.7 file involved. > > [~/Desktop/fltk-1.3.x-r6581]$ ldd fluid/fluid > linux-gate.so.1 => (0xffffe000) > libpng.so.3 => /usr/lib/libpng.so.3 (0xb7ee0000) > libz.so.1 => /lib/libz.so.1 (0xb7ecf000) > libjpeg.so.62 => /usr/lib/libjpeg.so.62 (0xb7eb0000) > libXext.so.6 => /usr/lib/libXext.so.6 (0xb7ea2000) > libXft.so.2 => /usr/lib/libXft.so.2 (0xb7e90000) > libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0xb7e8d000) > libpthread.so.0 => /lib/tls/libpthread.so.0 (0xb7e7a000) > libdl.so.2 => /lib/libdl.so.2 (0xb7e76000) > libX11.so.6 => /usr/lib/libX11.so.6 (0xb7da9000) > libstdc++.so.6 => > /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/libstdc++.so.6 (0xb7cd9000) > libm.so.6 => /lib/tls/libm.so.6 (0xb7cb6000) > libgcc_s.so.1 => /usr/lib/gcc/i686-pc-linux-gnu/3.4.5/libgcc_s.so.1 > (0xb7cad000) > libc.so.6 => /lib/tls/libc.so.6 (0xb7b91000) > libfontconfig.so.1 => /usr/lib/libfontconfig.so.1 (0xb7b6a000) > libXrender.so.1 => /usr/lib/libXrender.so.1 (0xb7b62000) > libexpat.so.0 => /usr/lib/libexpat.so.0 (0xb7b42000) > libfreetype.so.6 => /usr/lib/libfreetype.so.6 (0xb7ad0000) > /lib/ld-linux.so.2 (0xb7f15000)
This looks okay. Obviously fluid is linked statically (no ref. to a fltk .so file). >> BTW.: Did you "(sudo) make install" ? > > yes i did. Okay, good. Now the only theory I still have is that your previous 1.1.7 version has been installed in another path and that there are still some interfering versions. To test this, please do the following. If you can't interpret the results yourself, cut and paste the commands and post the results here again. Commands to execute (again, cd to your FLTK root dir first): echo $PATH which fltk-config which fluid ldd `which fluid` This should show us, if there is an old version of fluid (1.1.7) that is installed in another path, and that may be linked with the shareable fltk lib (.so). Then, start fluid by just typing "fluid" and look at the help/about menu: does it show "Version 1.1.7" or "Version 1.3.0" ? If you find that there is still something of your 1.1.7 installation, I'd recommend to use your distribution's packet manager (apt, rpm, ...) to remove the old installed version completely before proceeding. Albrecht _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
