On Fri, Oct 17, 2014 at 9:53 AM, Peter Foley wrote:
> Turns out this doesn't work if CROSS_COMPILE is set in the environment.
> I'll send another version shortly.
It seems there is more interested in cross-compiling Documentation
than I anticipated, so please ignore this as I'll be trying a
On Fri, Oct 17, 2014 at 9:53 AM, Peter Foley pefol...@pefoley.com wrote:
Turns out this doesn't work if CROSS_COMPILE is set in the environment.
I'll send another version shortly.
It seems there is more interested in cross-compiling Documentation
than I anticipated, so please ignore this as
On Wed, Oct 8, 2014 at 7:31 PM, Peter Foley wrote:
> Don't build Documentation targets when cross-compiling.
> They are only for build testing, and use the host headers and compiler
> which can cause cross-compiles to fail.
>
Turns out this doesn't work if CROSS_COMPILE is set in the
On Wed, Oct 8, 2014 at 7:31 PM, Peter Foley pefol...@pefoley.com wrote:
Don't build Documentation targets when cross-compiling.
They are only for build testing, and use the host headers and compiler
which can cause cross-compiles to fail.
Turns out this doesn't work if CROSS_COMPILE is set in
Don't build Documentation targets when cross-compiling.
They are only for build testing, and use the host headers and compiler
which can cause cross-compiles to fail.
Signed-off-by: Peter Foley
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Don't build Documentation targets when cross-compiling.
They are only for build testing, and use the host headers and compiler
which can cause cross-compiles to fail.
Signed-off-by: Peter Foley pefol...@pefoley.com
---
lib/Kconfig.debug | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
6 matches
Mail list logo