-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I debugged the problem a little more. First of all the good news:
8.119 works for me, 8.120 is broken. And the 8.120 version is also a
hell of a lot slower:

With 8.119 (works)
==========
/usr/src/linux-2.6.10$ time /usr/share/kernel-package/rules  
DEBIAN_REVISION=5:10.Custom  clean
[...]
real    0m10.120s
user    0m5.866s
sys     0m4.125s
==========

with 8.120 (broken, and prints a lot of warnings like
Makefile:484: .config: No such file or directory)
==========
/usr/src/linux-2.6.10$ time /usr/share/kernel-package/rules  
DEBIAN_REVISION=5:10.Custom  clean
[...]
/bin/sh: -c: line 0: unexpected EOF while looking for matching ``'
/bin/sh: -c: line 1: syntax error: unexpected end of file
[...]
real    1m17.266s
user    0m49.161s
sys     0m26.579s
==========

What really goes wrong in 8.120 is that when calling
"$(deb_rule) unpatch_now" in the real_stamp_clean target, the
$(EXTRA_VERSION) var is not empty as it should be. It is in fact the string
"make[2]: Entering directory `/usr/src/linux-2.6.10'  make[2]: Leaving 
directory `/usr/src/linux-2.6.10'"
Thus the obscure error message. I did found out that by adding the following
line after the ifneq check in /usr/share/kernel-package/rule:
[...]
ifneq ($(strip $(EXTRA_VERSION)),)
$(error XXX$(EXTRA_VERSION)XXX)
[...]

Why it fails like this however I don't know.


I think you should revert back to the old grep calls for EXTRA_VERSION
and the other vars. And it would be very much faster: right now the linux
kernel Makefile is parsed hundreds of times because it is included in
kernel_versions.mk.


Regards,
  Bastian
- -- 
  ,''`.                  Bastian Kleineidam
 : :' :                    GnuPG SchlÃssel
 `. `'    gpg --keyserver wwwkeys.pgp.net --recv-keys 32EC6F3E
   `-

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFCETHueBwlBDLsbz4RAmeQAKCwM1bAZq9E57eeMZhVqfe1xwdShQCgk85m
iEbdv5T94RIVDlzJvquBl6w=
=wc6w
-----END PGP SIGNATURE-----


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to