From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Mon, 7 Apr 2014 13:46:43 +0200 Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-04-05 In-Reply-To: <20140407114337.GB544@arch.cereza> References: <20140406063010.119BC100CBA@stock.ovh.net> <20140406110837.45baff8e@skate> <20140407111824.GA544@arch.cereza> <20140407132720.699be504@skate> <20140407114337.GB544@arch.cereza> Message-ID: <20140407134643.591875e7@skate> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Dear Ezequiel Garcia, On Mon, 7 Apr 2014 08:43:37 -0300, Ezequiel Garcia wrote: > OK, let me try to explain this better. If we have a (not too dirty) way of > running some script over the linux headers after an external toolchain has > been installed, we can "sanitize" them. > > In other words, we'd be doing the "make headers_install" sed magic ourselves, > given the Sourcery people forgot about it. > > Maybe adding something to toolchain-external.mk would work? > Let me do some tests to see if this works. We can certainly do some magic in toolchain-external.mk for specific toolchains. I just hope the magic is not too horrible :-) Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com