Hi, it took me a while to realize something in portage or elsewhere overwrites the URL printed by gcc when it dies. The current output is: Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.gentoo.org/> for instructions. After some poking around I see gcc gives (or used to give): Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://www.gnu.org/software/gcc/bugs.html> for instructions. I bet somebody wanted Gentoo users to report compiler issue to Gentoo bugzilla. Fine, but either point to a specific page describing how to obtain the gcc dump files and pre-processed source files needed by gcc developers or leave the URL as it is. Pointing one to http://bugs.gentoo.org/ is silly, sorry to say that. An example of former output: http://gcc.gnu.org/bugzilla/show_bug.cgi?id=7936 My current case (bug #448122) -- see the gentoo-specific URL below: /usr/bin/x86_64-pc-linux-gnu-g++ -c -Wall -Wno-format-y2k -pthread -pipe -msse -msse2 -msse3 -mssse3 -msse4.1 -msse4.2 -msse4 -march=native -fPIC -O9 -finline-functions -fstrict-aliasing -ffast-math -fomit-frame-pointer -DNDEBUG -D_LARGEFILE_SOURCE -D_LARGEFILE64_SOURCE -D_FILE_OFFSET_BITS=64 -D_MT -D_REENTRANT -D_THREAD_SAFE -I/var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/inc -I/var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/include /var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/src/algo/blast/api/blast_seqinfosrc_aux.cpp -o blast_seqinfosrc_aux.o /var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/src/algo/blast/api/objmgr_query_data.cpp: In constructor 'ncbi::objects::CNCBIpaa_Base::CNCBIpaa_Base()': /var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/src/algo/blast/api/objmgr_query_data.cpp:464:1: internal compiler error: Segmentation fault Please submit a full bug report, with preprocessed source if appropriate. See <http://bugs.gentoo.org/> for instructions. make[4]: *** [objmgr_query_data.o] Error 1 make[4]: *** Waiting for unfinished jobs.... rm .core_phi_gapalign.c .core_blast_extend.c .core_blast_diagnostics.c .core_blast_seg.c .core_hspfilter_collector.c .core_blast_engine.c .core_blast_sw.c .core_blast_posit.c .core_blast_hspstream.c .core_ncbi_math.c .core_ncbi_std.c .core_link_hsps.c .core_phi_lookup.c .core_blast_psi.c .core_pattern.c .core_blast_psi_priv.c .core_blast_tune.c .core_blast_query_info.c .core_blast_filter.c .core_hspfilter_culling.c .core_blast_message.c .core_blast_options.c .core_blast_seqsrc.c .core_split_query.c .core_blast_aascan.c .core_gencode_singleton.c .core_greedy_align.c .core_blast_parameters.c .core_blast_itree.c .core_index_ungapped.c .core_blast_dynarray.c .core_gapinfo.c .core_na_ungapped.c .core_blast_hits.c .core_phi_extend.c .core_blast_traceback.c .core_matrix_freq_ratios.c .core_blast_lookup.c .core_blast_encoding.c .core_blast_gapalign.c .core_blast_program.c .core_blast_util.c .core_blast_setup.c .core_lookup_wrap.c .core_blast_nascan.c .core_aa_ungapped.c .core_blast_nalookup.c .core_blast_aalookup.c .core_blast_stat.c .core_blast_kappa.c .core_hspfilter_besthit.c .core_lookup_util.c make[4]: Leaving directory `/var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/build/algo/blast/api' FAILED: src/algo/blast/api/Makefile.xblast.lib make[4]: Entering directory `/var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/build/algo/blast/api' /bin/rm -f libxblast.so .xblast.dep .libxblast.so.stamp /bin/rm -f /var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/lib/libxblast.so /var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/status/.xblast.dep make[4]: Leaving directory `/var/tmp/portage/sci-biology/ncbi-tools++-9.0.0/work/ncbi_cxx--9_0_0/GCC463-ReleaseMTDLL64/build/algo/blast/api'
toolchain.eclass, lines 1900-, gcc_version_patch()
there is no such thing as separate bug urls depending on the type of bug gcc itself hit. Gentoo is doing the correct thing and point users at the distro-specific bugzilla. expecting the upstream bugzilla is wrong. perhaps a gcc-specific page could be put together and we could point to that, but i don't really see much advantage. if you know wtf you're doing, then the bug url output from gcc is entirely useless -- you know where the right sites are what to report to each. if you have no idea wtf you're doing, then pointing to the main bugzilla page is correct. it has info for reporting bugs, searching for existing reports, and links to actually file new ones. the point of distros is to be the initial triage point, not for upstream to be.
