Hello Manoj, Manoj Srivastava schrieb am Sat 29. Apr, 21:22 (-0500): > tags 365434 +moreingo > thanks > > Hi, > > You have cut out the critical portions of the log which would > display what make-kpg called, but it seems like the call was:
It was /usr/bin/make ARCH=powerpc zImage > /usr/bin/make ARCH=powerpc prepare > /home/joerg/Tmp/kernel/linux-2.6.17-rc2/scripts/gcc-version.sh: > line 13: printf: 4: invalid number > /home/joerg/Tmp/kernel/linux-2.6.17-rc2/scripts/gcc-version.sh: > line 13: printf: 0: invalid number > > Sounds like a bug in the kernel sources. Can you say why you > don't think so? Because I can compile the kernel without make-kpkg without this error. Is it possible, that make-kpkg has problems with a gcc anywhere else than /usr/bin? I've a link on /usr/bin/colorgcc in ~/bin (which is in PATH). If I run make-kpkg with the environment variable MAKEFLAGS=CC=/usr/bin/gcc I have no problems. Mhmm, it seems the problem has something to do with colorgcc. I can build the kernel with colorgcc and without make-kpkg and I can build it without colorgcc and with make-kpkg. The symlink in ~/bin seems to not cause the trouble. If I link ccache as gcc to my ~/bin make-kpkg can build the kernel. I didn't see any clue in colorgcc that might cause that gcc do not find his environment. Bye, Jörg. -- Diskusion "Pascal vs. Rest der Welt": 30 Aug 2000 00:13:11 GMT, Adrian Knoth <[EMAIL PROTECTED]> Und selbst wenn eure 100000 Zeilen-Programme noch so oft unter Windows verwendet werden: mit einem Handwagen fährt man nicht Formel-1.
pgp5peHIoGlOS.pgp
Description: PGP signature
