On 9 April 2015 at 21:43, Stefan Weil wrote:
> My fork also contains additional code which would need much work
> to integrate it in the official QEMU (MIPS AR7 with WLAN router emulation,
> Raspberry Pi emulation and other parts which are not always working).
As an aside, if you're interested in
> On 09 Apr 2015, at 20:58, Peter Maydell wrote:
>
> On 9 April 2015 at 18:41, Stefan Weil wrote:
>> I think -mthreads is essential (needed for thread local storage),
>> and -D_POSIX=1 is also needed for 64 bit builds.
>
> My 64-bit builds worked without either of these things...
I tried with
Am 09.04.2015 um 21:44 schrieb Liviu Ionescu:
hmmm... things get complicated, even messier. :-(
Windows support _is_ complicated, yes.
There is MinGW32, MinGW-w64, Cygwin, Cygwin64 (list incomplete).
And some versions of MinGW-w64 are incompatible because they
changed their name mangling, so
> On 09 Apr 2015, at 20:58, Peter Maydell wrote:
>
> On 9 April 2015 at 18:41, Stefan Weil wrote:
>> I think -mthreads is essential (needed for thread local storage),
>> and -D_POSIX=1 is also needed for 64 bit builds.
>
> My 64-bit builds worked without either of these things...
hmmm... thin
On 9 April 2015 at 18:41, Stefan Weil wrote:
> I think -mthreads is essential (needed for thread local storage),
> and -D_POSIX=1 is also needed for 64 bit builds.
My 64-bit builds worked without either of these things...
-- PMM
Am 09.04.2015 um 16:07 schrieb Liviu Ionescu
On 09 Apr 2015, at 10:40, Liviu Ionescu wrote:
I guess you either tweaked the pkg-config to find them, or you set some
environment variables before configure.
...
can you share these details too? I want to reproduce "exactly" your environment.
Her
> On 09 Apr 2015, at 10:40, Liviu Ionescu wrote:
> I guess you either tweaked the pkg-config to find them, or you set some
> environment variables before configure.
> ...
> can you share these details too? I want to reproduce "exactly" your
> environment.
the reason I ask for these details is
> On 09 Apr 2015, at 08:12, Stefan Weil wrote:
>
> The first four are custom packages, and you can get them from
> http://qemu.weilnetz.de/debian/.
> The last one is Wheezy specific and not needed.
ok, got them, installed them and got no errors, they are now listed by dpkg -l
> The gtk custom
Am 08.04.2015 um 22:27 schrieb Liviu Ionescu:
On 08 Apr 2015, at 09:20, Stefan Weil wrote:
Here is my package list (from Debian Jessie):
ii binutils-mingw-w64-i686 2.22-8+deb7u2+2+deb7u1amd64
Cross-binutils for Win32 (x86) using MinGW-w64
ii binutils-mingw-w64-x86-64 2.22-8+d
> On 08 Apr 2015, at 09:20, Stefan Weil wrote:
>
> Here is my package list (from Debian Jessie):
>
> ii binutils-mingw-w64-i686 2.22-8+deb7u2+2+deb7u1amd64
> Cross-binutils for Win32 (x86) using MinGW-w64
> ii binutils-mingw-w64-x86-64 2.22-8+deb7u2+2+deb7u1amd64
On 8 April 2015 at 15:13, Liviu Ionescu wrote:
> p.s. I'm always amazed when for exact tasks, like complex
> builds, people prefer narrative recipes instead of ready
> to run scripts...
I agree generally, though this one is tedious because it
involves several different machines. The reason it end
> On 08 Apr 2015, at 02:10, Peter Maydell wrote:
>
> ... I dug out my
> notes on my setup at the time. ...
> but at the time (about June last year) this was a reproducible
> recipe that other people were able to use to build working
> w64 binaries.
thank you, Peter, I'll first try to reproduce
> On 08 Apr 2015, at 09:20, Stefan Weil wrote:
>
> ... Here is my package list (from Debian Jessie):
>
> ii binutils-mingw-w64-i686 2.22-8+deb7u2+2+deb7u1amd64
> Cross-binutils for Win32 (x86) using MinGW-w64
> ii binutils-mingw-w64-x86-64 2.22-8+deb7u2+2+deb7u1amd64
> On 08 Apr 2015, at 09:20, Stefan Weil wrote:
>
> ../../../configure --cross-prefix=x86_64-w64-mingw32-
> --enable-trace-backend=stderr --extra-cflags=-Wno-missing-format-attribute &&
> make
>
> ... mingw-w64.Here is my package list (from Debian Jessie):
ok
I'm just installing a new Win 8
Am 08.04.2015 um 00:45 schrieb Liviu Ionescu:
On 08 Apr 2015, at 01:36, Peter Maydell wrote:
No, I built an actual 64 bit Windows binary and it worked.
ok, then it must be only a matter of configure, which does not detect running
on mingw-w64 to set the required options (perhaps like -mthrea
On 7 April 2015 at 23:45, Liviu Ionescu wrote:
>> On 08 Apr 2015, at 01:36, Peter Maydell wrote:
>>
>> No, I built an actual 64 bit Windows binary and it worked.
>
> ok, then it must be only a matter of configure, which does not
> detect running on mingw-w64 to set the required options
> (perhap
> On 08 Apr 2015, at 01:36, Peter Maydell wrote:
>
> No, I built an actual 64 bit Windows binary and it worked.
ok, then it must be only a matter of configure, which does not detect running
on mingw-w64 to set the required options (perhaps like -mthreads -D_POSIX=1),
and I need to set them
On 7 April 2015 at 22:46, Liviu Ionescu wrote:
>
>> On 08 Apr 2015, at 00:30, Peter Maydell wrote:
>>
>> On 7 April 2015 at 22:21, Liviu Ionescu wrote:
>>> I could not identify if the problem is within qemu or mingw-w64,
>>> but I would not rule out a problem in qemu. I would first suspect
>>> a
> On 08 Apr 2015, at 00:46, Liviu Ionescu wrote:
>
> ... the 64-bit Windows build prepared by Stefan Weil seems to be done with
> the old mingw-w32 on Windows, not mingw-w64.
correction, I'm no longer convinced this is true, the build might be done with
mingw-w64, but with a lot of extra opti
> On 08 Apr 2015, at 00:30, Peter Maydell wrote:
>
> On 7 April 2015 at 22:21, Liviu Ionescu wrote:
>> I could not identify if the problem is within qemu or mingw-w64,
>> but I would not rule out a problem in qemu. I would first suspect
>> a customisation made especially for mingw-w32, which is
On 7 April 2015 at 22:21, Liviu Ionescu wrote:
> I could not identify if the problem is within qemu or mingw-w64,
> but I would not rule out a problem in qemu. I would first suspect
> a customisation made especially for mingw-w32, which is not
> appropriate for the 64-bit version of mingw-w64.
I
I was too optimistic, my 64-bit Windows build of the ARM emulator is not
functional. :-(
I also tested other 64-bit builds of qemu-system-arm made with mingw-w64 and
they are also not functional, they generally crash with some nasty DLL errors
when emulation is about to start (for example 0xc00
22 matches
Mail list logo
