-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

Am Di den 10. Jun 2014 um  8:11 schrieb Manoj Srivastava:
>         I can't see what could have changed since 13.007 (I stidued the
>  git diff, and have failed to spot a change that is likely to have
>  caused this problem).

The only change that I could spot, that might add the problem is:
   +Recommends: =R kernel-common

I'm not sure, but could it be that replacements are not allowed in
Recommends line? Just a guess.

> Also, I can't reproduce this, so I am a little
>  bit stumpe3d as to how to proceed.

That's sad. For me the problem always occurs. I have no way to work
around it.

I again looked what could make this problem appear and the only think
that might weight the build is "export CONCURRENCY_LEVEL=8".

> > By the way, with the commands above, on old days menuconfig was only
> > called once (in configure call) but since some years it gets called
> > every time, so tree times at all.
> 
>         Unless you are constantly changing the configuration every time
>  you call make-kpkg, there is no need for the --config option.

Well, the man page says that this parameter only tell make-kpkg which
target it should use when called with "configure" target. (And in fact,
that was the fact in old days.) I have all options in an $OPTIONS string
when compiling. Thats the reason why I specify it with every call.

As I understand the way it works, the configure target touches a file
that should be checked for existance afterwards.

>         If you do change your kernel config for every build, I am
>  intrigued by your work-flow. I tend to just keep different .config
>  files around, and swap them in and out in my wrapper script, rather
>  than editing the configuration on the fly.

I do not change my kernel config every time. In fact I copy the
.config file from my old kernel in the root of the new before
proceeding.

But I want to start configure once for a new kernel to see new
configurations options.

(And to repeat once, I always start with a clean linux-x.y.z and modules
directory before the configure call to make-kpkg. That includes to apply
debian-logo-2.6.31.gz patch and maybe others that are needed for current
kernels. (To compile nvidia or to fix bugs that was recently found.) Ah
yes, that patching stuff was something that was done by make-kpkg long
before too.)

Regards
   Klaus
- -- 
Klaus Ethgen                              http://www.ethgen.ch/
pub  4096R/4E20AF1C 2011-05-16   Klaus Ethgen <[email protected]>
Fingerprint: 85D4 CA42 952C 949B 1753  62B3 79D0 B06F 4E20 AF1C
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQGcBAEBCgAGBQJTltHXAAoJEKZ8CrGAGfashkEMAKyIvxq+/6VeWO/KMCSt812j
8rxj9/gc94KjZsH/b7kXE3wCrERD1Cg2/Th3+D62URqSB445pFCiGJz59V9upQ+b
NtvKwWUOU6V6TbpuW5uEgpfSQYgkcX98zbU5pwZPTCItY4vlKgozJEDivDhoEE3s
fo79w8EZBJ6MOe85J3ouuqkeMbaWKI/kUa/2W6WqnSuGYmtYKOY0RTw4O5zksqDV
i7tq7l28IQdCPaD4S6vcfZVLiDC1gOayyMWw8K1+OlgXNAlRydFrBmxzOEfs3fIP
FJt0DdQMs1YH2SN1PJFaXVsGJvmrAC3EsIi8IHz6sqrH07a6uuG4fgu6Sl8LWets
5BN71xMmxp+b0pRfn7PLfjNafVhNCF+w3qlxcc08JdY6SRzjqGm02khLRnFpXIPw
AzTyylowGlqW2+liV441jpGZHuyvl1RfBGWZNzmPUsoCQStAkS1cSJtN7suaEMiW
ypFj5ex+kBXstnsjDe2LsAmjqX2vudu35RODD0f3qw==
=9Tc9
-----END PGP SIGNATURE-----


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

Reply via email to