On Thu, Nov 20, 2014 at 6:17 PM, Laszlo Papp lp...@kde.org wrote:
On Tue, Nov 4, 2014 at 11:48 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Mon, 2014-11-03 at 17:29 +, Laszlo Papp wrote:
we have a tool that we run during our make run, but this tool is
hard-coded for 32
On Tue, Nov 4, 2014 at 11:48 AM, Richard Purdie
richard.pur...@linuxfoundation.org wrote:
On Mon, 2014-11-03 at 17:29 +, Laszlo Papp wrote:
we have a tool that we run during our make run, but this tool is
hard-coded for 32 bit. It depends on software like ncurses. I could
add
On Mon, 2014-11-03 at 17:29 +, Laszlo Papp wrote:
we have a tool that we run during our make run, but this tool is
hard-coded for 32 bit. It depends on software like ncurses. I could
add ncurses-native in an ideal world; no problem.
The problem is that my host environment is 64 bit
Hi,
we have a tool that we run during our make run, but this tool is
hard-coded for 32 bit. It depends on software like ncurses. I could
add ncurses-native in an ideal world; no problem.
The problem is that my host environment is 64 bit currently and it is
not possible to migrate the whole
Forgot to mention, but any nice workarounds are appreciated. I have a
few ideas, but they are all a bit ugly and non-robust.
On Mon, Nov 3, 2014 at 5:29 PM, Laszlo Papp lp...@kde.org wrote:
Hi,
we have a tool that we run during our make run, but this tool is
hard-coded for 32 bit. It depends
