From d5aca39f485bf46e6d77b7fb05eaf71b8ea51bee Mon Sep 17 00:00:00 2001
From: galjonsfigur <44552519+galjonsfigur@users.noreply.github.com>
Date: Fri, 23 Nov 2018 19:02:07 +0100
Subject: [PATCH] Fix build problem with luac.cross when DEVELOPMENT_USE_GDB is
 used (#2569)

---
 app/lua/lauxlib.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/app/lua/lauxlib.c b/app/lua/lauxlib.c
index 22ef0b9b..eb1665ad 100644
--- a/app/lua/lauxlib.c
+++ b/app/lua/lauxlib.c
@@ -958,12 +958,12 @@ LUALIB_API void luaL_assertfail(const char *file, int line, const char *message)
 #endif
 }
 
-#ifdef DEVELOPMENT_USE_GDB
+#if defined(DEVELOPMENT_USE_GDB) && !defined(LUA_CROSS_COMPILER)
 /*
  *  This is a simple stub used by lua_assert() if DEVELOPMENT_USE_GDB is defined.
  *  Instead of crashing out with an assert error, this hook starts the GDB remote
  *  stub if not already running and then issues a break.  The rationale here is 
- *  that when testing the developer migght be using screen/PuTTY to work ineractively
+ *  that when testing the developer might be using screen/PuTTY to work interactively
  *  with the Lua Interpreter via UART0.  However if an assert triggers, then there 
  * is the option to exit the interactive session and start the Xtensa remote GDB 
  * which will then sync up with the remote GDB client to allow forensics of the error.