Le 23/11/2015 15:23, John Paul Adrian Glaubitz a écrit :
> On 11/19/2015 01:52 PM, Laurent Vivier wrote:
>> I didn't really search the reason of that before, but:
>>
>> Socketcall 20 seems to be sendmmsg() (and 19 is recvmmsg()).
>>
>> I think it should be easy to add as the do_sendmmsg() and do_
On 11/19/2015 01:52 PM, Laurent Vivier wrote:
> I didn't really search the reason of that before, but:
>
> Socketcall 20 seems to be sendmmsg() (and 19 is recvmmsg()).
>
> I think it should be easy to add as the do_sendmmsg() and do_recvmmsg()
> already exist in linux-user/syscall.c
I'm not sure
On 11/19/2015 01:52 PM, Laurent Vivier wrote:
> Socketcall 20 seems to be sendmmsg() (and 19 is recvmmsg()).
>
> I think it should be easy to add as the do_sendmmsg() and do_recvmmsg()
> already exist in linux-user/syscall.c
Alright, I might have a look later. In case you have already done that
y
On 19/11/2015 13:20, John Paul Adrian Glaubitz wrote:
> On 11/19/2015 12:29 PM, Laurent Vivier wrote:
>> revert:
>>
>> linux-user: add netlink audit
>> linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT
>> linux-user: add rtnetlink(7) support
>
> Indeed, that worked!
>
> I am now getti
On 11/19/2015 12:29 PM, Laurent Vivier wrote:
> revert:
>
> linux-user: add netlink audit
> linux-user: support netlink protocol NETLINK_KOBJECT_UEVENT
> linux-user: add rtnetlink(7) support
Indeed, that worked!
I am now getting an error message about an unsupported socketcall, but
otherwise it
On 19/11/2015 12:13, John Paul Adrian Glaubitz wrote:
> On 11/19/2015 11:48 AM, John Paul Adrian Glaubitz wrote:
>> This is absolutely fantastic. Now for some compile tests :).
>
> Ok, something still seems to be missing. While running gpg --recv-keys
> worked fine, running apt-get update afterw
On 11/19/2015 11:48 AM, John Paul Adrian Glaubitz wrote:
> This is absolutely fantastic. Now for some compile tests :).
Ok, something still seems to be missing. While running gpg --recv-keys
worked fine, running apt-get update afterwards gets stuck immediately:
root@z6:/# apt-get update
0% [Conne
On 19/11/2015 11:40, John Paul Adrian Glaubitz wrote:
> Hi Laurent!
>
> I gave your working tree qemu-m68k [1] a try with sbuild today.
>
> I configured the sources as follows:
>
> $ ./configure --target-list=m68k-linux-user --static
see below.
> Then ran "make && make install".
>
> Then cr
On 11/19/2015 11:44 AM, Laurent Vivier wrote:
> By default cpu is "any", which is a coldfire target, you must add
> "--m68k-default-cpu=m68040" on the configure line, or add a wrapper in
> the chroot to call qemu-m68k with "-cpu m68040".
Indeed.
root@z6:..chroots/sid-m68k-sbuild> chroot .
bash: w
Hi Laurent!
I gave your working tree qemu-m68k [1] a try with sbuild today.
I configured the sources as follows:
$ ./configure --target-list=m68k-linux-user --static
Then ran "make && make install".
Then created an m68k chroot using:
$ debootstrap --no-check-gpg --variant=buildd --foreign --a
10 matches
Mail list logo