On Fri, 2019-03-15 at 11:12 +, Daniel P. Berrangé wrote:
> Thinking some more, I expect what happened is that the Debian 32-bit x86
> arch did indeed generate code compatible with i386 and thus this library
> path got set. These days no one cares about true i386 compat, so the
> compiler
On Fri, Mar 15, 2019 at 12:06:13PM +0100, Andrea Bolognani wrote:
> On Fri, 2019-03-15 at 11:27 +0100, Erik Skultety wrote:
> > On Thu, Mar 14, 2019 at 05:52:17PM +, Daniel P. Berrangé wrote:
> > > Although the toolchain binaries for 32-bit x86 are using the ABI
> > > i686-linux-gnu, the
On Fri, 2019-03-15 at 11:27 +0100, Erik Skultety wrote:
> On Thu, Mar 14, 2019 at 05:52:17PM +, Daniel P. Berrangé wrote:
> > Although the toolchain binaries for 32-bit x86 are using the ABI
> > i686-linux-gnu, the library install directory is strangely named
> > with the different
On Fri, Mar 15, 2019 at 11:27:48AM +0100, Erik Skultety wrote:
> On Thu, Mar 14, 2019 at 05:52:17PM +, Daniel P. Berrangé wrote:
> > Although the toolchain binaries for 32-bit x86 are using the ABI
> > i686-linux-gnu, the library install directory is strangely named
> > with the different
On Thu, Mar 14, 2019 at 05:52:17PM +, Daniel P. Berrangé wrote:
> Although the toolchain binaries for 32-bit x86 are using the ABI
> i686-linux-gnu, the library install directory is strangely named
> with the different i386-linux-gnu.
>
> Signed-off-by: Daniel P. Berrangé
> ---
so the patch
Although the toolchain binaries for 32-bit x86 are using the ABI
i686-linux-gnu, the library install directory is strangely named
with the different i386-linux-gnu.
Signed-off-by: Daniel P. Berrangé
---
guests/lcitool | 11 ++-
1 file changed, 10 insertions(+), 1 deletion(-)
diff --git
