On at least one occasion a patch (nominally from Gentoo) caused an ICE. Do not ask for details because this is general problem. By just restarting with a clean source package from gcc.gnu.org with the same date that ICE disappeared. Gentoo is well entitled to deny assistance or follow-up on clearly marked packages. However, Gentoo then should refrain from messing things up via non gcc.gnu.org patches. That I would have made a fool of myself by submitting this particular non-bug to gcc.gnu.org is irrelevant; but causing unecessary work at gcc.gnu.org would have been detrimental to the overall gcc community. About one or two weeks later I submitted an ICE, which was promptly recognized as being real was fixed within days and turned out to be a classical Kernighan_Ritchie type oversight at the margins of of that particular new (Tree-SSA) optimization. I have been a user of GNU packages for about twenty years and in general bugs are fixed by the time organizations like Gentoo come out with patches that really apply to already obsolete versions of the package in question. One example of this are patches and other items like eclasses from the gcc-3.y.z applied to gcc-3.y+1.z; or even worse to gcc-4.y'.z'. BTW, similar remarks apply to the Linux-kernel. This practice only leads, at least myself, to loose confidence and to use the strict Gentoo approach to dealing only with aministrivia and with inconsequential or no longer actively mantained packages. If you people are interested in many other suggestions I am at your disposal; however, I am not intersted in becoming a (so-called) Gentoo developer because I consider about 50% of the things apparently dear to the in group at Gentoo to be irrelevant or even a nuisance. (e.g. forcing ldconfig after just "emerging" kernel-source, header-files, and other packages that have absolutely no DLL content. Regards Ray Best Regards
(In reply to comment #0) > On at least one occasion a patch (nominally from Gentoo) caused an ICE. Do not > ask for details because this is general problem. Feel free to take your complaints to gentoo-dev mailing list, bugzilla is not a suitable place for generic moaning and discussions. If you have a real bug where a *specific* patch breaks something, then file a new bug, otherwise go to mailing lists. Thanks.
yeah anyways
i really have no idea what you're proposing be done to "fix" the current situation do not add any patches to gcc ? most of our patches come from upstream, either via backporting or until the next revision is out in terms of things like PIE/SSP/boundschecking, those are hardened efforts that arent going away if you're concerned that you're hitting an ICE and it's due to Gentoo modifications, simply re-emerge gcc with USE=vanilla and test again
Whenever an ICE occurs with a Gentoo-patched compiler, you get this: Please submit a full bug report, with preprocessed source if appropriate. See <URL:http://bugs.gentoo.org/> for instructions. Note the direction to submit bugs here, _NOT_ direct to gcc.gnu.org. This is precisely because the compiler is not identical to the upstream release and we need to see if it's something we have caused first. Gentoo is not alone in this - most if not all distributions deliver compilers that are patched to some degree. Resolving invalid, as (1) the report is not a bug, (2) we already direct Gentoo users to file bugs here, not directly with gcc.gnu.org and (3) gcc-4 is still masked.
pkg_postinst() { toolchain_pkg_postinst einfo "This gcc-4 ebuild is provided for your convenience, and the use" einfo "of this compiler is not supported by the Gentoo Developers." einfo "Please file bugs related to gcc-4 with upstream developers." einfo "Compiler bugs should be filed at http://gcc.gnu.org/bugzilla/" } The above is directly taken from gcc-4.1.0xxx.ebuild This clearly demonstrates that either: 1) Wthin the Gentoo organization the left hand doe not know what the right hand is doing. Claiming that gcc-4.1xxx is masked is no excuse. 2) The advice to use "USE=vanilla" demonstrates complete ignorance on the party of the writer. I tried it with both gcc and gtk (picked at random) and it is ignored both cases. For gtk it at least acknowledges the "USE=vanilla" in the "--ask" case befor ignoring it. This is a serious systemic bug, because it adversly causes wasted effort beyond the Gentoo community.
(In reply to comment #5) > pkg_postinst() { > toolchain_pkg_postinst > > einfo "This gcc-4 ebuild is provided for your convenience, and the use" > einfo "of this compiler is not supported by the Gentoo Developers." > einfo "Please file bugs related to gcc-4 with upstream developers." > einfo "Compiler bugs should be filed at http://gcc.gnu.org/bugzilla/" > } > The above is directly taken from gcc-4.1.0xxx.ebuild > This clearly demonstrates that either: > 1) Wthin the Gentoo organization the left hand doe not know what the right hand > is doing. Claiming that gcc-4.1xxx is masked is no excuse. gcc-4.1 is not patched. Its the weekly snapshot taken from upstream.
(In reply to comment #5) > The above is directly taken from gcc-4.1.0xxx.ebuild > This clearly demonstrates that either: > 1) Wthin the Gentoo organization the left hand doe not know what the right > hand is doing. Claiming that gcc-4.1xxx is masked is no excuse. not really, when you say 'gcc-4.x.x' we think 'gcc-4.0.x' because that is the only support gcc-4 version in Gentoo. gcc-4.1 is not supported because it isnt stable for general use atm. also, we dont apply any Gentoo patches to this so your argument about Gentoo patches doesnt apply to this series. > 2) The advice to use "USE=vanilla" demonstrates complete ignorance on the > party of the writer. no reason to be a dickhead > I tried it with both gcc and gtk (picked at random) and > it is ignored both cases. For gtk it at least acknowledges the "USE=vanilla" > in the "--ask" case befor ignoring it. this bug report is about gcc, not gtk ... i never said USE=vanilla works on all packages, just that it works with gcc. as for it being ignored, it works just fine for me. compare the output of `USE=vanilla emerge gcc` and `USE=-vanilla emerge gcc` using any version other than gcc-4.1.x
Nothing useful is going to come of this. If you have an actual bug, please let us know.
Please! PLEASE! Do not make me take this to the GNU/Open-Source community at large. You are harming fundamental work on GCC. This potentiall affects on only the Gentoo community but the whole of Linux/GNU, BSD and OS X. Now to the specific demonstrations of incompetence: A) this is the complete gcc-4.0.1.ebuild. Enough Said. # Copyright 1999-2006 Gentoo Foundation # Distributed under the terms of the GNU General Public License v2 # $Header: /var/cvsroot/gentoo-x86/sys-devel/gcc/gcc-4.0.1.ebuild,v 1.12 2006/01/07 03:31:54 vapier Exp $ PATCH_VER="1.0" PATCH_GCC_VER="4.0.1" UCLIBC_VER="1.0" UCLIBC_GCC_VER="4.0.0" PIE_VER="8.7.8" PIE_GCC_VER="4.0.0" PP_VER="" HTB_VER="1.00" ETYPE="gcc-compiler" # whether we should split out specs files for multiple {PIE,SSP}-by-default # and vanilla configurations. SPLIT_SPECS=no #${SPLIT_SPECS-true} hard disable until #106690 is fixed inherit toolchain DESCRIPTION="The GNU Compiler Collection. Includes C/C++, java compilers, pie+ssp extensions, Haj Ten Brugge runtime bounds checking" HOMEPAGE="http://www.gnu.org/software/gcc/gcc.html" LICENSE="GPL-2 LGPL-2.1" KEYWORDS="-*" RDEPEND="!sys-devel/hardened-gcc || ( app-admin/eselect-compiler >=sys-devel/gcc-config-1.3.10 ) >=sys-libs/zlib-1.1.4 amd64? ( multilib? ( >=app-emulation/emul-linux-x86-glibc-1.1 ) ) fortran? ( dev-libs/gmp dev-libs/mpfr ) !build? ( gcj? ( gtk? ( >=x11-libs/gtk+-2.2 ) >=media-libs/libart_lgpl-2.1 ) >=sys-libs/ncurses-5.2-r2 nls? ( sys-devel/gettext ) )" if [[ ${CATEGORY} != cross-* ]] ; then RDEPEND="${RDEPEND} elibc_glibc? ( >=sys-libs/glibc-2.3.6 )" fi DEPEND="${RDEPEND} >=sys-apps/texinfo-4.2-r4 >=sys-devel/bison-1.875 >=${CATEGORY}/binutils-2.15.94" PDEPEND="|| ( app-admin/eselect-compiler sys-devel/gcc-config ) x86? ( !nocxx? ( !elibc_uclibc? ( !build? ( =virtual/libstdc++-3.3 ) ) ) )" pkg_postinst() { toolchain_pkg_postinst einfo "This gcc-4 ebuild is provided for your convenience, and the use" einfo "of this compiler is not supported by the Gentoo Developers." einfo "Please file bugs related to gcc-4 with upstream developers." einfo "Compiler bugs should be filed at http://gcc.gnu.org/bugzilla/" } B The following script file (easily reproduced if you dont trust me and if you know some UNIX). Note that neither 'USE="vanilla"' nor the --nocolor is headed by emerge causing the difficulty in reading it. However the evidence is clear. Script started on Fri Jan 13 19:25:29 2006 [01;31mi786-63[01;34m ~ #[00m USE="vanilla" emerge -B --nocolor --ask =gcc-4.0.1 ]2;Started emerge on: Jan 13, 2006 19:27:58]2; *** emerge --buildpkgonly --nocolor --ask --buildpkg =gcc-4.0.1 These are the packages that I would merge, in order: Calculating dependencies - \ ...done! [ebuild UD] sys-devel/gcc-4.0.1 [4.0.2-r2] USE="vanilla*" Do you want me to merge these packages? [Yes/No] y >>> emerge (1 of 1) sys-devel/gcc-4.0.1 to / ]2; >>> emerge (1 of 1) sys-devel/gcc-4.0.1 to /]2;emerge: (1 of 1) sys-devel/gcc-4.0.1 Cleanmv: cannot stat `/var/tmp/portage/gcc-4.0.1/temp/environment': No such file or directory ]2;emerge: (1 of 1) sys-devel/gcc-4.0.1 Compile>>> checksums files ;-) gcc-3.3.5-r1.ebuild >>> checksums files ;-) gcc-3.2.3-r4.ebuild >>> checksums files ;-) gcc-3.1.1-r2.ebuild >>> checksums files ;-) gcc-3.3.6.ebuild >>> checksums files ;-) gcc-2.95.3-r9.ebuild >>> checksums files ;-) gcc-3.4.3.20050110-r2.ebuild >>> checksums files ;-) gcc-3.3.2-r7.ebuild >>> checksums files ;-) gcc-4.0.2-r3.ebuild >>> checksums files ;-) gcc-3.3.5.20050130-r2.ebuild >>> checksums files ;-) gcc-3.4.1-r3.ebuild >>> checksums files ;-) gcc-3.4.4-r1.ebuild >>> checksums files ;-) gcc-3.2.2.ebuild >>> checksums files ;-) gcc-4.0.1.ebuild >>> checksums files ;-) gcc-4.1.0_beta20060106.ebuild >>> checksums files ;-) gcc-3.4.3-r1.ebuild >>> checksums files ;-) gcc-3.3.5.20050130-r1.ebuild >>> checksums files ;-) gcc-3.4.5.ebuild >>> checksums files ;-) files/digest-gcc-3.4.3.20050110-r2 >>> checksums files ;-) files/pro-police-docs.patch >>> checksums files ;-) files/digest-gcc-3.1.1-r2 >>> checksums files ;-) files/digest-gcc-3.2.3-r4 >>> checksums files ;-) files/digest-gcc-3.3.2-r7 >>> checksums files ;-) files/digest-gcc-3.3.5-r1 >>> checksums files ;-) files/digest-gcc-3.4.1-r3 >>> checksums files ;-) files/digest-gcc-3.4.3-r1 >>> checksums files ;-) files/digest-gcc-3.4.4-r1 >>> checksums files ;-) files/digest-gcc-3.3.5.20050130-r1 >>> checksums files ;-) files/digest-gcc-3.3.5.20050130-r2 >>> checksums files ;-) files/gcc331_use_multilib.amd64.patch >>> checksums files ;-) files/gcc-configure-LANG.patch >>> checksums files ;-) files/fix_libtool_files.sh >>> checksums files ;-) files/digest-gcc-4.0.2-r3 >>> checksums files ;-) files/digest-gcc-3.2.2 >>> checksums files ;-) files/digest-gcc-3.3.6 >>> checksums files ;-) files/digest-gcc-3.4.5 >>> checksums files ;-) files/digest-gcc-4.0.1 >>> checksums files ;-) files/digest-gcc-2.95.3-r9 >>> checksums files ;-) files/mkinfodir >>> checksums files ;-) files/gcc-spec-env.patch >>> checksums files ;-) files/digest-gcc-4.1.0_beta20060106 >>> checksums files ;-) files/scan_libgcc_linked_ssp.sh >>> checksums files ;-) files/awk/fixlafiles.awk >>> checksums files ;-) files/awk/scanforssp.awk >>> checksums files ;-) files/3.2.1/gcc32-strip-dotdot.patch >>> checksums files ;-) files/3.2.1/gcc31-loop-load-final-value.patch >>> checksums files ;-) files/3.2.1/gcc32-sparc32-hack.patch >>> checksums files ;-) files/3.2.1/gcc32-athlon-alignment.patch >>> checksums files ;-) files/3.2.1/gcc32-arm-reload1-fix.patch >>> checksums files ;-) files/3.2.1/gcc32-arm-disable-mathf.patch >>> checksums files ;-) files/3.2.2/gcc32-pr7768.patch >>> checksums files ;-) files/3.2.2/gcc322-ggc_page-speedup.patch >>> checksums files ;-) files/3.2.2/gcc-3.2.2-no-COPYING-cross-compile.patch >>> checksums files ;-) files/3.2.2/gcc-3.2.2-cross-compile.patch >>> checksums files ;-) files/3.2.2/gcc32-pr8213.patch >>> checksums files ;-) files/3.2.3/gcc32-mklibgcc-serialize-crtfiles.patch >>> checksums files ;-) files/3.2.3/gcc32-c++-classfn-member-template.patch >>> checksums files ;-) files/3.2.3/gcc323-gentoo-branding.patch >>> checksums files ;-) files/3.2.3/gcc-3.2.3-mergel-fix.patch >>> checksums files ;-) files/3.2.3/gcc-3.2.3-move-propolice-into-glibc.patch >>> checksums files ;-) files/3.2.3/gcc323-hppa-default_assemble_visibility.patch >>> checksums files ;-) files/3.2.3/gcc-323-propolice-version.patch >>> checksums files ;-) files/3.3.1/gcc331-pp-fixup.patch >>> checksums files ;-) files/3.3.2/gcc332-altivec-fix.patch >>> checksums files ;-) files/3.3.2/gcc332-gentoo-branding.patch >>> checksums files ;-) files/3.3.3/gcc333-debian-arm-ldm.patch >>> checksums files ;-) files/3.3.3/gcc-uclibc-3.3-loop.patch >>> checksums files ;-) files/3.3.3/gcc-3.3.3-norelro.patch >>> checksums files ;-) files/3.3.3/gcc333-debian-arm-getoff.patch >>> checksums files ;-) files/3.3.3/gcc-3.3.3-uclibc-add-ssp.patch >>> checksums files ;-) files/3.3.3/gcc333_pre20040408-stack-size.patch >>> checksums files ;-) files/3.3.4/libffi-without-libgcj.patch >>> checksums files ;-) files/3.3.5/gcc-3.3.5-ffecom_gfrt_basictype-prototype.patch >>> checksums files ;-) files/3.3.5/gcc-3.3.5-no-COPYING-cross-compile.patch >>> checksums files ;-) files/3.3.6/gcc-3.3.6-cross-compile.patch >>> checksums files ;-) files/3.4.0/gcc-3.4.0-cc1-no-stack-protector.patch >>> checksums files ;-) files/3.4.0/gcc34-reiser4-fix.patch >>> checksums files ;-) files/3.4.1/gcc-3.4.1-glibc-is-native.patch >>> checksums files ;-) files/3.4.1/gcc-3.4.1-mips-n64only.patch >>> checksums files ;-) files/3.4.1/gcc-3.4.1-mips-n32only.patch >>> checksums files ;-) files/3.4.1/gcc-3.4.1-r2-gentoo-branding.patch >>> checksums files ;-) files/3.4.2/gcc34-fix-sse2_pinsrw.patch >>> checksums files ;-) files/3.4.2/gcc34-m32-no-sse2.patch >>> checksums files ;-) files/3.4.2/gcc-3.4.x-mips-add-march-r10k.patch >>> checksums files ;-) files/3.4.2/810-arm-bigendian-uclibc.patch >>> checksums files ;-) files/3.4.2/gcc-3.4.2-mips-ip28_cache_barriers-v2.patch >>> checksums files ;-) files/3.4.3/libffi-without-libgcj.patch >>> checksums files ;-) files/3.4.3/gcc-3.4.3-cross-compile.patch >>> checksums files ;-) files/3.4.3/libffi-nogcj-lib-path-fix.patch >>> checksums files ;-) files/3.4.3/libssp.patch >>> checksums files ;-) files/3.4.4/gcc-3.4.4-softfloat.patch >>> checksums files ;-) files/3.4.4/gcc-3.4.4-cross-compile.patch >>> checksums files ;-) files/4.0.2/gcc-4.0.2-cross-compile.patch >>> checksums files ;-) files/stubs/gcc-3.3-htb-stub.patch >>> checksums files ;-) files/stubs/gcc-4.0-htb-stub.patch >>> checksums files ;-) files/stubs/gcc-3.4-ssp-stub.patch >>> checksums files ;-) files/stubs/gcc-3.3-ssp-stub.patch >>> checksums files ;-) files/stubs/gcc-3.4-htb-stub.patch >>> checksums files ;-) files/stubs/gcc-4.0-ssp-stub.patch >>> checksums src_uri ;-) gcc-4.0.1.tar.bz2 >>> checksums src_uri ;-) gcc-4.0.0-uclibc-patches-1.0.tar.bz2 >>> checksums src_uri ;-) gcc-4.0.1-patches-1.0.tar.bz2 >>> checksums src_uri ;-) gcc-4.0.0-piepatches-v8.7.8.tar.bz2 >>> Unpacking source... >>> Unpacking gcc-4.0.1.tar.bz2 to /var/tmp/portage/gcc-4.0.1/work >>> Unpacking gcc-4.0.1-patches-1.0.tar.bz2 to /var/tmp/portage/gcc-4.0.1/work >>> Unpacking gcc-4.0.0-uclibc-patches-1.0.tar.bz2 to /var/tmp/portage/gcc-4.0.1/work >>> Unpacking gcc-4.0.0-piepatches-v8.7.8.tar.bz2 to /var/tmp/portage/gcc-4.0.1/work [32;01m*[0m Applying stub patch for htb ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying stub patch for ssp ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Applying upstream pie patches ... [32;01m*[0m 00_all_gcc-4.0-cvs-incompat.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 00_all_gcc-4.0-cvs-start_endfile.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 03_all_gcc-3.4.0-v8.7.6.1-pie-arm.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Done with patching [32;01m*[0m Applying non-default pie patches ... [32;01m*[0m 02_all_gcc-3.4.3-v8.7.1-pie-rs6000-nondefault.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-3.4.3-v8.7.6.7-pie-sparc-nondefault.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Done with patching [32;01m*[0m Applying default pie patches ... [32;01m*[0m 00_all_gcc-3.4.3-v8.7.6.7-incompat-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 01_all_gcc-4.0-v8.7.8-pie-generic-default-boundschecking-no.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 01_all_gcc-4.0-v8.7.8-pie-generic-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-3.4.3-v8.7.6.7-pie-alpha-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-3.4.3-v8.7.6.7-pie-arm-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-3.4.3-v8.7.6.7-pie-ia64-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-3.4.3-v8.7.6.7-pie-rs6000-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m 02_all_gcc-4.0-v8.7.6.7-pie-sparc-default.patch.bz2 ... [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Done with patching QA Notice: USE Flag 'hardened' not in IUSE for sys-devel/gcc-4.0.1 QA Notice: USE Flag 'hardened' not in IUSE for sys-devel/gcc-4.0.1 [32;01m*[0m Replacing obsolete head/tail with POSIX compliant ones [32;01m*[0m - fixed contrib/test_summary [32;01m*[0m - fixed boehm-gc/configure [32;01m*[0m - fixed fastjar/configure [32;01m*[0m - fixed fixincludes/configure [32;01m*[0m - fixed gcc/configure [32;01m*[0m - fixed intl/configure [32;01m*[0m - fixed libada/configure [32;01m*[0m - fixed libcpp/configure [32;01m*[0m - fixed libffi/configure [32;01m*[0m - fixed libgfortran/configure [32;01m*[0m - fixed libiberty/configure [32;01m*[0m - fixed libjava/configure [32;01m*[0m - fixed libmudflap/configure [32;01m*[0m - fixed libobjc/configure [32;01m*[0m - fixed libstdc++-v3/configure [32;01m*[0m - fixed zlib/configure [32;01m*[0m - fixed ltcf-c.sh [32;01m*[0m - fixed ltcf-cxx.sh [32;01m*[0m - fixed ltcf-gcj.sh [32;01m*[0m - fixed ltmain.sh [32;01m*[0m patching gcc version: 4.0.1 (Gentoo 4.0.1, pie-8.7.8) [32;01m*[0m Running elibtoolize in: gcc-4.0.1 [32;01m*[0m Applying portage-1.4.0.patch ... [32;01m*[0m Applying relink-1.4.0a-GCC3.0-2.patch ... [32;01m*[0m Applying sed-1.4.0.patch ... [32;01m*[0m Applying tmp-1.3.5.patch ... [32;01m*[0m Using GNU config files from /usr/share/libtool [32;01m*[0m Updating libjava/libltdl/config.sub [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Updating config.sub [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Updating libjava/libltdl/config.guess [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Updating config.guess [A[75G [34;01m[ [32;01mok[34;01m ][0m [32;01m*[0m Fixing misc issues in configure files [32;01m*[0m Updating configure... [A[75G [34;01m[ [32;01mok[34;01m ][0m >>> Source unpacked. >>> Compiling source in /var/tmp/portage/gcc-4.0.1/work/gcc-4.0.1 ... [32;01m*[0m CFLAGS="-O2 -pipe -mtune=pentium3" [32;01m*[0m CXXFLAGS="-O2 -pipe -mtune=pentium3" [32;01m*[0m Configuring gcc ... [32;01m*[0m running gcc-compiler-configure [32;01m*[0m configuring for GCC_LANG: c,c++,f95 [32;01m*[0m PREFIX: /usr [32;01m*[0m BINPATH: /usr/i686-pc-linux-gnu/gcc-bin/4.0.1 [32;01m*[0m LIBPATH: /usr/lib/gcc/i686-pc-linux-gnu/4.0.1 [32;01m*[0m DATAPATH: /usr/share/gcc-data/i686-pc-linux-gnu/4.0.1 [32;01m*[0m STDCXX_INCDIR: /usr/lib/gcc/i686-pc-linux-gnu/4.0.1/include/g++-v4 [32;01m*[0m Configuring GCC with: --prefix=/usr --bindir=/usr/i686-pc-linux-gnu/gcc-bin/4.0.1 --includedir=/usr/lib/gcc/i686-pc-linux-gnu/4.0.1/include --datadir=/usr/share/gcc-data/i686-pc-linux-gnu/4.0.1 --mandir=/usr/share/gcc-data/i686-pc-linux-gnu/4.0.1/man --infodir=/usr/share/gcc-data/i686-pc-linux-gnu/4.0.1/info --with-gxx-include-dir=/usr/lib/gcc/i686-pc-linux-gnu/4.0.1/include/g++-v4 --host=i686-pc-linux-gnu --build=i686-pc-linux-gnu --disable-altivec --enable-nls --without-included-gettext --with-system-zlib --disable-checking --disable-werror --disable-libunwind-exceptions --disable-multilib --disable-libmudflap --disable-libgcj --enable-languages=c,c++,f95 --enable-shared --enable-threads=posix --enable-__cxa_atexit --enable-clocale=gnu creating cache ./config.cache checking host system type... i686-pc-linux-gnu checking target system type... i686-pc-linux-gnu checking build system type... i686-pc-linux-gnu checking for a BSD compatible install... /bin/ginstall -c checking whether ln works... yes checking whether ln -s works... yes checking for gcc... gcc checking whether the C compiler (gcc -O2 -pipe -mtune=pentium3 ) works... yes checking whether the C compiler (gcc -O2 -pipe -mtune=pentium3 ) is a cross-compiler... no checking whether we are using GNU C... yes checking whether gcc accepts -g... yes checking for gnatbind... gnatbind checking whether compiler driver understands Ada... no checking how to compare bootstrapped objects... cmp --ignore-initial=16 $$f1 $$f2 checking for correct version of gmp.h... yes checking for MPFR... yes *** This configuration is not supported in the following subdirectories: target-libffi target-boehm-gc target-zlib target-libjava target-libmudflap target-libada zlib fastjar target-libobjc (Any other directories should still work fine.) checking for bison... bison checking for bison... bison -y checking for gm4... no checking for gnum4... no checking for m4... m4 checking for flex... flex checking for flex... flex checking for makeinfo... makeinfo checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar checking for i686-pc-linux-gnu-as... i686-pc-linux-gnu-as checking for i686-pc-linux-gnu-dlltool... no checking for dlltool... dlltool checking for i686-pc-linux-gnu-ld... /usr/lib/gcc/i686-pc-linux-gnu/4.1.0-beta20060106/../../../../i686-pc-linux-gnu/bin/ld checking for i686-pc-linux-gnu-nm... i686-pc-linux-gnu-nm checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib checking for i686-pc-linux-gnu-windres... no checking for windres... windres checking for i686-pc-linux-gnu-objcopy... i686-pc-linux-gnu-objcopy checking for i686-pc-linux-gnu-objdump... i686-pc-linux-gnu-objdump checking for i686-pc-linux-gnu-ar... i686-pc-linux-gnu-ar checking for i686-pc-linux-gnu-as... i686-pc-linux-gnu-as checking for i686-pc-linux-gnu-dlltool... no checking for dlltool... dlltool checking for i686-pc-linux-gnu-ld... i686-pc-linux-gnu-ld checking for i686-pc-linux-gnu-nm... i686-pc-linux-gnu-nm checking for i686-pc-linux-gnu-ranlib... i686-pc-linux-gnu-ranlib checking for i686-pc-linux-gnu-windres... no checking for windres... windres checking whether to enable maintainer-specific portions of Makefiles... no checking if symbolic links between directories work... yes updating cache ./config.cache creating ./config.status creating Makefile /usr/portage/sys-devel/gcc/gcc-4.0.1.ebuild: src_compile aborted; exiting. sandbox: Caught signal 2 in pid 20069 Exiting on signal 2 ]2; *** terminating.]2;root@i786-63:~[01;31mi786-63[01;34m ~ #[00m [Kexit exit Script done on Fri Jan 13 19:29:57 2006 C The follwing comes from /var/tmp/portage/gcc-4.0.1/work/patches: ================ === W[hat]TF === ================ Gentoo patchsets that have grown too large to keep on the rsync mirrors have been moved to our cvs tree. From there, we bundle up all the whee little patches into a tarball and distribute it via our public mirroring system. If you want specific info about a patch (like wtf it does or whose great idea it was to change the code), read the patch ! We try to fill out the top of them with useful info such as what it does, why it's needed, bug reports, original creators, etc... For simple patches, we reserve the right to assume your IQ is greater than absolute 0 and figure out what it does w/out an explanation. If, by some miracle of science, it falls below the absolute 0 mark, you should help mankind by finding some scientists and letting them probe you with their ... erm ... probes. ================= === W[here]TF === ================= For those with CVS access, you want the 'src/patchsets' dir inside of the 'gentoo' cvs module. For those w/out CVS access, this URL should help you: http://viewcvs.gentoo.org/src/patchsets/?root=gentoo It should be pretty easy to find your way around, you're a big boy after all. It amuses me how stupidity is demonstrated by using offensive and unprofessional language.
Stop bugspamming us with crap - seriously. Trolling is NOT welcome here.
CLOSED
(In reply to comment #9) > Please! PLEASE! Do not make me take this to the GNU/Open-Source community at > large. You are harming fundamental work on GCC. This potentiall affects on > only the Gentoo community but the whole of Linux/GNU, BSD and OS X. not quite sure what the point of this is, probably safe to write it off as pointless rambling > Now to the specific demonstrations of incompetence: > > A) this is the complete gcc-4.0.1.ebuild. Enough Said. thanks, we know how to read ebuilds in editors using 4.0.1 is irrelevant seeing as how it's going to be cut from portage shortly ... if you read the 4.0.2 ebuild you'll see how the upstream warning has been cut long ago > B The following script file (easily reproduced if you dont trust me and if you > know some UNIX). Note that neither 'USE="vanilla"' nor the --nocolor is headed > by emerge causing the difficulty in reading it. However the evidence is clear. again, being a dickhead wont get you anywhere, but speaking of "knowing some UNIX", you should learn to redirect into a log file and post attachments the hardened patches have been split off from USE=vanilla, so in order to avoid adding them, you'll also need USE="nossp nopie" > It amuses me how stupidity is demonstrated by using offensive and > unprofessional language. when you get some spare time, you should think about picking up a sense of humor at any rate, you have yet to show anything useful here
