linux-kernel - Re: `make checkstack' and cross-compilation

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061201153021.GA4332@ccure.user-mode-linux.org>
Date:	Fri, 1 Dec 2006 10:30:21 -0500
From:	Jeff Dike <jdike@...toit.com>
To:	Geert Uytterhoeven <Geert.Uytterhoeven@...ycom.com>
Cc:	Linux Kernel Development <linux-kernel@...r.kernel.org>
Subject: Re: `make checkstack' and cross-compilation

On Fri, Dec 01, 2006 at 02:58:16PM +0100, Geert Uytterhoeven wrote:
> Makefile has:
> | # Use $(SUBARCH) here instead of $(ARCH) so that this works for UML.
> | # In the UML case, $(SUBARCH) is the name of the underlying
> | # architecture, while for all other arches, it is the same as $(ARCH).
> | checkstack:
> |         $(OBJDUMP) -d vmlinux $$(find . -name '*.ko') | \
> |         $(PERL) $(src)/scripts/checkstack.pl $(SUBARCH)
> 
> While this may fix `make checkstack' for UML, it breaks cross-compilation.
> E.g. when cross-compiling for PPC on ia32, ARCH=powerpc, but SUBARCH=i386.
> 
> Probably it should use SUBARCH if ARCH=um, and ARCH otherwise?

Whoops, you're right.  

Do you have a patch?  If not, I'll make one.

And, do you have a cross-compilation environment which tests this?

				Jeff

-- 
Work email - jdike at linux dot intel dot com
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/