On Sun, Feb 25, 2007 at 12:48:26AM -0600, Manoj Srivastava wrote:
>        So, $(DEBDIR)/ruleset/misc/version_vars.mk is called before
> $(DEBDIR)/ruleset/architecture.mk;  and the former should define
> $(VERSION) and friends.

It looks like the problem is related to $(KERNEL_VERSION.  If I add

    @echo KERNEL_ARCH=$(KERNEL_ARCH) VERSION=$(VERSION)

to the "all" rule of debian/rules I get:

    $ make -f debian/rules all
    /bin/sh: line 0: [: -lt: unary operator expected
    [...etc...]
    KERNEL_ARCH=powerpc VERSION=
    nothing to be done.

whereas this works:

    $ make -f debian/rules all KERNEL_ARCH=ppc 
    KERNEL_ARCH=ppc VERSION=2
    nothing to be done.

It appears that debian/ruleset/misc/version_vars.mk passes
ARCH=$(KERNEL_ARCH) when calling debian/ruleset/kernel_version.mk, which
doesn't work when KERNEL_ARCH=powerpc .

For reference, the order of files being opened follows (from a strace if
"make all").

    debian/rules
    debian/ruleset/common/archvars.mk
    .config
    debian/ruleset/common/pkgvars.mk
    debian/ruleset/common/install_cmds.mk
    debian/ruleset/common/debconf.mk
    debian/ruleset/local-vars.mk
    debian/ruleset/misc/defaults.mk
    debian/ruleset/misc/kernel_arch.mk
    debian/ruleset/misc/version_vars.mk
    debian/ruleset/architecture.mk
    debian/ruleset/arches/powerpc.mk
    debian/ruleset/arches/what_is_ppc_called_today.mk
    debian/ruleset/misc/pkg_names.mk
    /etc/kernel-pkg.conf
    debian/ruleset/misc/config.mk
    debian/ruleset/misc/initrd.mk
    debian/ruleset/misc/patches.mk
    debian/ruleset/misc/modules.mk
    debian/ruleset/misc/checks.mk
    debian/ruleset/common/targets.mk
    debian/ruleset/local.mk
    debian/ruleset/targets/target.mk
    debian/ruleset/targets/sanity_check.mk
    debian/ruleset/targets/source.mk
    debian/ruleset/targets/headers.mk
    debian/ruleset/targets/manual.mk
    debian/ruleset/targets/doc.mk
    debian/ruleset/targets/image.mk
    debian/ruleset/modules.mk

--bod


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

Reply via email to