On 1 November 2016 at 19:21, Richard Henderson wrote:
> On 11/01/2016 12:17 PM, Peter Maydell wrote:
>> On 1 November 2016 at 17:51, Richard Henderson wrote:
>>>
>>> The usual pain point for me is building for 32-bit on a 64-bit
>>> system, where there is no cross-prefix that one can use, and
>>>
On 11/01/2016 12:17 PM, Peter Maydell wrote:
On 1 November 2016 at 17:51, Richard Henderson wrote:
The usual pain point for me is building for 32-bit on a 64-bit
system, where there is no cross-prefix that one can use, and
PKG_CONFIG_PATH and --extra-cflags are the only changes.
That sounds l
On 1 November 2016 at 17:51, Richard Henderson wrote:
> The usual pain point for me is building for 32-bit on a 64-bit
> system, where there is no cross-prefix that one can use, and
> PKG_CONFIG_PATH and --extra-cflags are the only changes.
That sounds like a bug in how the 32-bit compilers work
On Tue, Nov 01, 2016 at 04:26:57PM +, Peter Maydell wrote:
> On 1 November 2016 at 16:20, Daniel P. Berrange wrote:
> > On Tue, Nov 01, 2016 at 09:34:24AM -0600, Richard Henderson wrote:
> >> On 11/01/2016 06:07 AM, Richard Henderson wrote:
> >> > V2, now with more windows workarounds. I'll n
On 11/01/2016 11:43 AM, Daniel P. Berrange wrote:
It was a particular pain-point for me when doing mingw builds, where
I would typically use 'PKG_CONFIG_PATH=/blah ./configure' so that I
didn't permanently pollute my shell with mingw32 pkg-config env
The usual pain point for me is building for
On 11/01/2016 08:26 AM, Peter Maydell wrote:
i686-w64-mingw32 builds fail to link :-(
exec.o: In function `qemu_flockfile':
/home/petmay01/linaro/qemu-for-merges/include/sysemu/os-win32.h:110:
undefined reference to `_imp___lock_file'
exec.o: In function `qemu_funlockfile':
/home/petmay01/linaro
On 1 November 2016 at 16:20, Daniel P. Berrange wrote:
> On Tue, Nov 01, 2016 at 09:34:24AM -0600, Richard Henderson wrote:
>> On 11/01/2016 06:07 AM, Richard Henderson wrote:
>> > V2, now with more windows workarounds. I'll note that I have not
>> > been 100% successful in actually building a mi
On Tue, Nov 01, 2016 at 09:34:24AM -0600, Richard Henderson wrote:
> On 11/01/2016 06:07 AM, Richard Henderson wrote:
> > V2, now with more windows workarounds. I'll note that I have not
> > been 100% successful in actually building a mingw64 image. But
> > at least the error Peter saw with v1 is
On 1 November 2016 at 15:34, Richard Henderson wrote:
> Bah. I think I've been tripped up by the fact that we fail to preserve
> PKG_CONFIG_PATH when re-running configure via make. We really should
> finally fix that -- it's really really annoying when building a non-default
> config.
FWIW this
On 11/01/2016 06:07 AM, Richard Henderson wrote:
V2, now with more windows workarounds. I'll note that I have not
been 100% successful in actually building a mingw64 image. But
at least the error Peter saw with v1 is fixed.
I'll report on the other mingw64 failures under separate cover.
Bah.
On 1 November 2016 at 12:07, Richard Henderson wrote:
> V2, now with more windows workarounds. I'll note that I have not
> been 100% successful in actually building a mingw64 image. But
> at least the error Peter saw with v1 is fixed.
>
> I'll report on the other mingw64 failures under separate
V2, now with more windows workarounds. I'll note that I have not
been 100% successful in actually building a mingw64 image. But
at least the error Peter saw with v1 is fixed.
I'll report on the other mingw64 failures under separate cover.
r~
The following changes since commit e80b4b8fb6babc
12 matches
Mail list logo
