Dave Yost wrote: > I suggest that fink be enhanced to do what some other systems have been > doing lately: package up all the info for a bug report and send it to > the right place (after the user has a chance to look it over and say OK). > > The above functionality would replace the stdout dump of do-it-yourself > "Please submit a full bug report" instructions exemplified below, which > occurred as the first thing I tried to do after a clean install of fink > 029.9 on my 10.6.1 system with Xcode 3.2.1.
The problem is that bugs are rarely adhering to a standard that would allow an automatic treatment (otherwise they would probably not be there.) You case is a good example for this. [] > ... > /sw/src/fink.build/gcc44-4.4.1-1000/darwin_objdir/./prev-gcc/xgcc > -B/sw/src/fink.build/gcc44-4.4.1-1000/darwin_objdir/./prev-gcc/ > -B/sw/lib/gcc4.4/i686-apple-darwin10/bin/ -c -g -O2 > -fomit-frame-pointer -DIN_GCC -W -Wall -Wwrite-strings > -Wstrict-prototypes -Wmissing-prototypes -Wcast-qual > -Wold-style-definition -Wc++-compat -Wmissing-format-attribute -pedantic > -Wno-long-long -Wno-variadic-macros -Wno-overlength-strings > -DHAVE_CONFIG_H -I. -I. -I../../gcc-4.4.1/gcc -I../../gcc-4.4.1/gcc/. > -I../../gcc-4.4.1/gcc/../include -I../../gcc-4.4.1/gcc/../libcpp/include > -I/sw/include -I../../gcc-4.4.1/gcc/../libdecnumber > -I../../gcc-4.4.1/gcc/../libdecnumber/dpd -I../libdecnumber > -I/sw/include -I/sw/include -DCLOOG_PPL_BACKEND -I/sw/include > ../../gcc-4.4.1/gcc/dbxout.c -o dbxout.o > ../../gcc-4.4.1/gcc/dbxout.c: In function 'dbxout_begin_simple_stabs': > ../../gcc-4.4.1/gcc/dbxout.c:584: internal compiler error: in > ggc_set_mark, at ggc-page.c:1319 > Please submit a full bug report, > with preprocessed source if appropriate. > See <http://gcc.gnu.org/bugs.html> for instructions. It is not fink that is speaking here, but gcc. So what would you think is "the right place" this should be sent to, Fink or gnu? And what would "all the info for a bug report" be? [] > ../../gcc-4.4.1/gcc/config/i386/sync.md: In function 'recog_35': > ../../gcc-4.4.1/gcc/config/i386/sync.md:30: internal compiler error: in > df_reg_chain_mark, at df-scan.c:4277 > Please submit a full bug report, > with preprocessed source if appropriate. > See <http://gcc.gnu.org/bugs.html> for instructions. Seeing that the bug seems to appear randomly, (a fact that an automated bug reporting system would probably have hidden), my wild guess is that you either have a shell startup script that sets a too small stacksize limit, or you have a hardware (perhaps memory) problem. -- Martin ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Fink-devel mailing list Fink-devel@lists.sourceforge.net http://news.gmane.org/gmane.os.apple.fink.devel Subscription management: https://lists.sourceforge.net/lists/listinfo/fink-devel
