Re: [RFC PATCH] Use target compiler for user binaries in samples/

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sun, 31 Mar 2013, Sam Ravnborg wrote:

> The user-space binaries build in samples/ uses the installed
> headers for the kernel.
> Therefore it is wrong that they use the host compiler
> to build the samples.
> 
> Following is an attempt to create some infrastructure
> for building user-space binaries that uses the uapi headers.
> 
> As my sparc cross toolchain does not supporting building
> user-space I have not been able to test this as good as I hoped...
> 
> But faking that my native gcc is a cross gcc seems to work.
> 
> This adds two new variables to the top-level Makefile:
> UAPICC and UAPICFLAGS
> 
> The architectures that supports both 32 and 64 bit set the
> appropriate flags in UAPICFLAGS.
> 
> scripts/Makefile.uapiprogs cantains all the infrastructure.
> 
> I updated the samples for hidraw and seccomp to use the new
> infrastructure.
> 
> The file says:
> +# Sample syntax (see Documentation/kbuild/makefiles.txt for reference)
> 
> But I did not bother to write this yet - awaiting feedback.

I generally like the idea.

It'd be nice to know whether this fixes the ARCH=sparc allyesconfig builds 
Fengguang has been reporting. Fengguang ... ?

Thanks,

-- 
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kbuild" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




[Index of Archives]     [Linux&nblp;USB Development]     [Linux Media]     [Video for Linux]     [Linux Audio Users]     [Yosemite Secrets]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux