Your message dated Thu, 12 Mar 2009 16:58:36 -0700 with message-id <20090312235836.GY25139@jade.home> and subject line has caused the Debian Bug report #404840, regarding colorgcc: Breaks kernel and some autoconf builds to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 404840: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=404840 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: colorgcc: Breaks kernel and some autoconf builds
- From: Christian Ohm <chr.ohm@gmx.net>
- Date: Thu, 28 Dec 2006 16:27:24 +0100
- Message-id: <20061228152724.GA21600@localdomain>
Package: colorgcc Version: 1.3.2.0-4 Severity: important Hi, I used to use colorgcc with /usr/local/bin/cc, c++, gcc, g++ symlinked to /usr/bin/colorgcc. Those symlinks used to work without problems, but since some time some builds fail. The first problem is that autoconf cannot find an ld: (example is from a local build of jack-audio-connection-kit_0.102.20-1 for x86) configure output: checking for ld used by cc... no configure: error: no acceptable ld found in $PATH The respective part of config.log isn't more enlightening: configure:4515: checking for ld used by cc configure:4585: result: no configure:4588: error: no acceptable ld found in $PATH I guess not all configures check for ld, so not all break. The second problem is in kernel builds. "make V=1 prepare" stops with the following output: "rm -f include/config/kernel.release echo 2.6.19-rt10 > include/config/kernel.release set -e; echo ' CHK include/linux/version.h'; mkdir -p include/linux/; (echo \#define LINUX_VERSION_CODE 132627; echo '#define KERNEL_VERSION(a,b,c) (((a) << 16) + ((b) << 8) + (c))';) < /var/src/linux-2.6.19-co/Makefile > include/linux/version.h.tmp; if [ -r include/linux/version.h ] && cmp -s include/linux/version.h include/linux/version.h.tmp; then rm -f include/linux/version.h.tmp; else echo ' UPD include/linux/version.h'; mv -f include/linux/version.h.tmp include/linux/version.h; fi CHK include/linux/version.h set -e; echo ' CHK include/linux/utsrelease.h'; mkdir -p include/linux/; if [ `echo -n "2.6.19-rt10" | wc -c ` -gt 64 ]; then echo '"2.6.19-rt10" exceeds 64 characters' >&2; exit 1; fi; (echo \#define UTS_RELEASE \"2.6.19-rt10\";) < include/config/kernel.release > include/linux/utsrelease.h.tmp; if [ -r include/linux/utsrelease.h ] && cmp -s include/linux/utsrelease.h include/linux/utsrelease.h.tmp; then rm -f include/linux/utsrelease.h.tmp; else echo ' UPD include/linux/utsrelease.h'; mv -f include/linux/utsrelease.h.tmp include/linux/utsrelease.h; fi CHK include/linux/utsrelease.h make -f scripts/Makefile.build obj=scripts/basic make -f scripts/Makefile.build obj=. mkdir -p arch/i386/kernel/ gcc -m32 -Wp,-MD,arch/i386/kernel/.asm-offsets.s.d -nostdinc -isystem /usr/lib/gcc/i486-linux-gnu/4.1.2/include -D__KERNEL__ -Iinclude -include include/linux/autoconf.h -Wall -Wundef -Wstrict-prototypes -Wno-trigraphs -fno-strict-aliasing -fno-common -Os -pipe -msoft-float -mpreferred-stack-boundary=2 -march=i686 -ffreestanding -maccumulate-outgoing-args -Iinclude/asm-i386/mach-default -pg -fno-omit-frame-pointer -fno-optimize-sibling-calls -fasynchronous-unwind-tables -g -fno-stack-protector -Wdeclaration-after-statement -Wno-pointer-sign -D"KBUILD_STR(s)=#s" -D"KBUILD_BASENAME=KBUILD_STR(asm_offsets)" -D"KBUILD_MODNAME=KBUILD_STR(asm_offsets)" -fverbose-asm -S -o arch/i386/kernel/asm-offsets.s arch/i386/kernel/asm-offsets.c In file included from include/asm/system.h:4, from include/asm/processor.h:18, from include/asm/atomic.h:5, from include/linux/crypto.h:20, from arch/i386/kernel/asm-offsets.c:7: include/linux/kernel.h:10:20: error: stdarg.h: No such file or directory In file included from include/asm/system.h:4, from include/asm/processor.h:18, from include/asm/atomic.h:5, from include/linux/crypto.h:20, from arch/i386/kernel/asm-offsets.c:7: include/linux/kernel.h:115: error: expected declaration specifiers or ‘...’ before ‘va_list’ include/linux/kernel.h:121: error: expected declaration specifiers or ‘...’ before ‘va_list’ include/linux/kernel.h:125: error: expected declaration specifiers or ‘...’ before ‘va_list’ include/linux/kernel.h:132: error: expected declaration specifiers or ‘...’ before ‘va_list’ include/linux/kernel.h:147: error: expected declaration specifiers or ‘...’ before ‘va_list’ In file included from include/acpi/acpi.h:61, from include/linux/suspend2.h:141, from include/linux/suspend.h:11, from arch/i386/kernel/asm-offsets.c:11: include/acpi/acpiosxf.h:260: error: expected declaration specifiers or ‘...’ before ‘va_list’ make[1]: *** [arch/i386/kernel/asm-offsets.s] Error 1 make: *** [prepare0] Error 2" Executing exactly the same gcc command that fails when run from make succeeds when run from the command line. I have tried several kernel versions, so it's not specific to the tree I used as example here. Both problems are gone when I remove the symlinks to colorgcc from /usr/local/bin, so the problem is with colorgcc, though only in some specific situations. Bye, Christian Ohm -- System Information: Debian Release: 4.0 APT prefers unstable APT policy: (900, 'unstable'), (800, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.17-beyond4 Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.utf8) Versions of packages colorgcc depends on: ii perl 5.8.8-7 Larry Wall's Practical Extraction ii perl-modules 5.8.8-7 Core Perl modules colorgcc recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message ---
- To: 404840-done@bugs.debian.org
- From: Ryan Niebur <ryanryan52@gmail.com>
- Date: Thu, 12 Mar 2009 16:58:36 -0700
- Message-id: <20090312235836.GY25139@jade.home>
Hi, seeing how you say it seems to work now, I am closing the bug. If you find additional problems please feel free to reopen it or create a new one. Thanks, Ryan -- _________________________ Ryan Niebur ryanryan52@gmail.comAttachment: signature.asc
Description: Digital signature
--- End Message ---