/bin/sh ../libtool --silent --tag=CXX --mode=compile i686-pc-linux-gnu-g++ -DHAVE_CONFIG_H -I. -I. -I.. -I./libical/src/libical -I./libical/src/libicalss -I./libical/src/libical -I./libical/src/libicalss -I./versit -I../ -I../ktnef -I../libemailfunctions -I../libkdepim -I/usr/kde/3.5/include -I/usr/qt/3/include -I. -DQT_THREAD_SUPPORT -D_REENTRANT -D_FILE_OFFSET_BITS=64 -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -O2 -march=i686 -pipe -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c -o vcaldrag.lo vcaldrag.cpp incidenceformatter.cpp: In member function 'virtual bool KCal::IncidenceFormatter::EventViewerVisitor::visit(KCal::Todo*)': incidenceformatter.cpp:553: internal compiler error: Segmentation fault Please submit a full bug report, I'll get around to that full bug report just as soon as I figure out where the file attachment feature I'm supposed to use is located. I'm not seeing it anywhere, so I can only guess that it is only available after I post the bug.
Created attachment 105155 [details] Textual information relating to the bug, like ... everything I could think of. It said "with preprocessed source if appropriate" but I haven't a clue how to do that. Someone will have to explain if it is needed. It also somewhere said "the bug is not reproducible, so it is likely a hardware or OS problem" but I'm not sure why it thinks it knows this. In any event, I tried the compile again, and it failed again, so I think it is reproducable, at least to some extent.
...and now I see this is at the top of the "most frequently reported bugs" list. I had the tab open, but it seems I forgot to look at it. Well... I guess I'll mark this as a duplicate, assuming no one can do anything about it. *** This bug has been marked as a duplicate of 20600 ***
On the other hand, I suppose the error message did ask that I please submit a bug report, so perhaps there is something else to this...
> I think it is reproducable, at least to some extent. I gave it another try, without changing anything, to see if it failed in exactly the same place, but it has compiled that package and moved on to others. In light of that, this is clearly just a problem with my computer, and so I'm marking it as closed again. ...but perhaps someone might want to remove that "please submit a full bug report" text, assuming it specifically appears when GCC segfaults. A link to a web page that suggests things such as first recompiling to see if the failure occurs in exactly the same file on exactly the same line could be helpful. Also, if that failed, I was going to try replacing the compiler with a script that, in the event the compiler segfaults, sleeps for a few minutes to let the CPU cool down, then runs the compiler again. BTW, thanks for Gentoo! It's awesome! It is so nice to have a system that only has the software that I want installed on it, and the fact that I can even install kernel patches with emerge was beyond my expectations. ...and those nifty USE flags are so much easier than figuring out what magic method each piece of software requires to add and remove features. Gentoo is just so much better than I expected it to be.
Oops, I forgot to close it. *** This bug has been marked as a duplicate of 20600 ***
Closing.
