[Top] [All Lists]

Re: [PATCH] samples/seccomp/Makefile: Do not build tests if cross-compil

To: Paul Gortmaker <>, David Daney <>
Subject: Re: [PATCH] samples/seccomp/Makefile: Do not build tests if cross-compiling for MIPS
From: Markos Chandras <>
Date: Mon, 17 Feb 2014 13:22:26 +0000
Cc: "" <>, "" <>
In-reply-to: <>
List-archive: <>
List-help: <>
List-id: linux-mips <>
List-owner: <>
List-post: <>
List-software: Ecartis version 1.0.0
List-subscribe: <>
List-unsubscribe: <>
Original-recipient: rfc822;
References: <> <> <>
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.3.0
On 02/14/2014 01:33 AM, Paul Gortmaker wrote:
On Thu, Feb 13, 2014 at 1:30 PM, David Daney <> wrote:
Really I think we should add a Kconfig item for this and disable the whole
directory for targets that do not support it.

Can we do something based on  CONFIG_CROSS_COMPILE vs. adding more Kconfig?


Hi Paul,

I am not sure how this would solve anything. CONFIG_CROSS_COMPILE could be empty, but you can still use 'make CROSS_COMPILE=mips-linux-foobar-' or whatever to cross-compile for MIPS. So using this symbol to disable tests does not seem right to me.

Another Kconfig symbol should be more appropriate but as far as I can see MIPS is the only architecture which has this problem (or I may have missed all{yes,mod}config failures from other architectures).

I still think that an "ifndef CONFIG_MIPS" is good enough for now until more architectures suffer from this problem in the future. So far (and looking at the git history of that file) other architectures managed to workaround this.


<Prev in Thread] Current Thread [Next in Thread>