On 6/9/22 11:04, Mattias Ellert wrote:
>>> Was this implemented?
>>> Mainly I'm asking if there is any point in clicking the give-back
>>> link
>>> on the builds that failed with the old set-up.
>>
>> Sorry, not yet, I had a busy week.
>>
>> I’ll try to get it done this week and will let you know.
mån 2022-05-23 klockan 09:56 +0200 skrev John Paul Adrian Glaubitz:
> Hi Matthias!
>
> > On May 23, 2022, at 9:43 AM, Mattias Ellert
> > wrote:
> >
> > mån 2022-05-16 klockan 10:28 +0200 skrev John Paul Adrian
> > Glaubitz:
> > > Hi Matthias!
> > >
> > > > On 5/16/22 10:24, Mattias Ellert
Hi Matthias!
> On May 23, 2022, at 9:43 AM, Mattias Ellert
> wrote:
>
> mån 2022-05-16 klockan 10:28 +0200 skrev John Paul Adrian Glaubitz:
>> Hi Matthias!
>>
>>> On 5/16/22 10:24, Mattias Ellert wrote:
>>> I have noticed that in addition to m68k and sh4, the builds also
>>> fail
>>> in the
mån 2022-05-16 klockan 10:28 +0200 skrev John Paul Adrian Glaubitz:
> Hi Matthias!
>
> On 5/16/22 10:24, Mattias Ellert wrote:
> > I have noticed that in addition to m68k and sh4, the builds also
> > fail
> > in the same way on the hppa host known as pasta, but when given
> > back
> > and run on
Hi Rob,
On Mon, May 16, 2022 at 2:51 PM Rob Landley wrote:
> QEMU's sh4 system emulation only has 64 megs ram, but you can add as much swap
> space as you like and the compiler's been happy with it so far. (Even when it
> gets a little thrashy, it stays in the host's page cache so it's all
>
On 5/16/22 03:28, John Paul Adrian Glaubitz wrote:
> Hi Matthias!
>
> On 5/16/22 10:24, Mattias Ellert wrote:
>> I have noticed that in addition to m68k and sh4, the builds also fail
>> in the same way on the hppa host known as pasta, but when given back
>> and run on a different hppa host
Hi Matthias!
On 5/16/22 10:24, Mattias Ellert wrote:
> I have noticed that in addition to m68k and sh4, the builds also fail
> in the same way on the hppa host known as pasta, but when given back
> and run on a different hppa host they succeed.
>
> E.g.
>
Hi!
Now the openssl3 transition is underway, and many more of the globus
packages fail in the same way.
My original idea that it was failing due to doxygen using an input
filter, seems to be incorrect. Only 4 of the globus packages uses an
input filter, an many more of them are failing than
Hi Laurent!
On 5/12/22 18:22, Laurent Vivier wrote:
>> I guess it's related to the glibc issue then [1].
>
> You can try by mounting your chroot on a non ext4 partition. It works well
> with btrfs.
>
> Ext4 stores a hash in a field that is normally an index, so a 64bit (host
> kernel long)
Le 12/05/2022 à 18:16, John Paul Adrian Glaubitz a écrit :
Hi!
Hi :)
On 5/12/22 18:10, Laurent Vivier wrote:
The flags are correct.
This can be tested with:
$ sudo chroot m68k-chroot sh -c 'echo $0'
sh
if the argument is not properly managed, you would have "/usr/bin/sh".
Hi!
On 5/12/22 18:10, Laurent Vivier wrote:
> The flags are correct.
>
> This can be tested with:
>
> $ sudo chroot m68k-chroot sh -c 'echo $0'
> sh
>
> if the argument is not properly managed, you would have "/usr/bin/sh".
OK, this is working properly:
root@z6:/srv/chroot>
Le 12/05/2022 à 17:51, John Paul Adrian Glaubitz a écrit :
On 5/12/22 17:45, Laurent Vivier wrote:
No, the 'F' means 'fix-binary':
The interpreter is loaded in memory once when the binfmt_misc is configured
(when
the configuration is written to /proc/sys/fs/binfmt_misc/register) from the host
On 5/12/22 17:45, Laurent Vivier wrote:
> No, the 'F' means 'fix-binary':
>
> The interpreter is loaded in memory once when the binfmt_misc is configured
> (when
> the configuration is written to /proc/sys/fs/binfmt_misc/register) from the
> host
> filesystem. So you don't need to put it in the
Le 12/05/2022 à 17:41, John Paul Adrian Glaubitz a écrit :
Hi Laurent!
The issue can be reproduced on a freshly installed Debian system.
Is the problem the additional "F" flag?
glaubitz@z6:/tmp/test> cat /proc/sys/fs/binfmt_misc/qemu-m68k
enabled
interpreter
Hi Laurent!
The issue can be reproduced on a freshly installed Debian system.
Is the problem the additional "F" flag?
glaubitz@z6:/tmp/test> cat /proc/sys/fs/binfmt_misc/qemu-m68k
enabled
interpreter /usr/libexec/qemu-binfmt/m68k-binfmt-P
flags: POCF
offset 0
magic
Hi Laurent!
On 5/10/22 23:48, Laurent Vivier wrote:
> Did you configure binfmt_misc to preserve argv0 [2] ?
>
> $ cat /proc/sys/fs/binfmt_misc/qemu-m68k
> enabled
> interpreter //qemu-m68k
> flags: POC
> offset 0
> magic 7f454c46010201020004
> mask
Le 10/05/2022 à 21:23, John Paul Adrian Glaubitz a écrit :
Hi!
On 4/27/22 11:19, John Paul Adrian Glaubitz wrote:
On 4/27/22 11:04, Laurent Vivier wrote:
Normally, since qemu v6.0.0 you can preserve argv[0]:
(...)
You need also kernel v5.12:
OK, I'm installing QEMU 6.2 and kernel 5.16 from
Hi!
On 4/27/22 11:19, John Paul Adrian Glaubitz wrote:
> On 4/27/22 11:04, Laurent Vivier wrote:
>> Normally, since qemu v6.0.0 you can preserve argv[0]:
>> (...)
>> You need also kernel v5.12:
>
> OK, I'm installing QEMU 6.2 and kernel 5.16 from backports on all QEMU
> buildds now. Let's see if
Hi Laurent!
On 4/27/22 11:04, Laurent Vivier wrote:
> Normally, since qemu v6.0.0 you can preserve argv[0]:
> (...)
> You need also kernel v5.12:
OK, I'm installing QEMU 6.2 and kernel 5.16 from backports on all QEMU
buildds now. Let's see if that helps.
Adrian
--
.''`. John Paul Adrian
Le 26/04/2022 à 21:24, John Paul Adrian Glaubitz a écrit :
Hi!
...
[2] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974004
Normally, since qemu v6.0.0 you can preserve argv[0]:
commit 6e1c0d7b951e19c53b8467e8bc4b71ee73a394ea
Author: Laurent Vivier
Date: Mon Feb 22 11:50:04 2021
Hi!
On 4/21/22 09:25, Mattias Ellert wrote:
> Doxygen uses popen to run filters. Is there an issue with using popen
> to run perl scripts on the buildds for m68k and sh4?
>
> The reason I ask is that I found this report in BTS:
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974004
> which
21 matches
Mail list logo
