On Fri, 06 Jan 2012 23:17:40 -0800, Richard Sanders <[email protected]> wrote:
>On Fri, 06 Jan 2012 04:16:06 -0800, Ian MacArthur ><[email protected]> wrote: > >>On 6 Jan 2012, at 08:33, Richard Sanders <[email protected]> wrote: >> >>> I have just done a clean install of Suse 12.1 on a 32 bit box. >>> >>> I compiled fltk-1.3.x-r9217 and then compiled a finished project that >>> runs on XP and Suse 11.3 (64 bit), On the Suse 12.1 I get predictable >>> crashes. I compiled fltk-1.3.x-r8695 and fltk-1.3.x-r9187 with the >>> same predictable results. >>> >>> There seems to be something broken with Suse 12.1, beware. >> >>Richard, >> >>Summarising your post, you are reporting that Suse 11.3 is OK in 64-bit >>builds, but that Suse 12.1 is "broken" in 32-bit builds; is that correct? >> >>Can you detail the crash behaviour, i.e. what triggers it, etc... >> >>Better yet, run it through gdb to see if that tell's us where the crash >>originates (though might need to clean and rebuild the FLTK libs with debug >>enabled to get enough details...) >>We can't preclude that we might be doing something wrong and in any case it >>would be useful to understand what causes the crash... >> >>FWIW, I only seem to have 32-bit Linux boxes right now and all work fine - >>though I don't have any Suse boxes, only ubuntu and fedora. > >I checked the GCC versions. Suse 12.1 has gone up to 4.6 while the >previous versions were 4.5. > >I installed Suse 12.1 on a spare drive and hunted down GCC 4.5 rather >than the default install of 4.6. In short, no crashes. > >Either GCC 4.6 is buggered or my install is. I will try un installing >GCC 4.6 tomorrow and then re install and see what that does. > >I did hunt down the crash points and note the file name and line >number but it is a bit premature to be looking at FLTK for errors. >A second opinion on GCC 4.6 might be in order. > >A note on suse 12.1. The XFCE in rather nice neither spartan nor >bloated out like the Mint Linux XFCE. Xununtu did not like my raid >card when it came to the point of writing GRUB. This whole problem I had turns out to be codeblocks. I built a new project in codeblocks and copied my sources into the new dir. That fixed it. Weird! _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
