Hello!
On 11/1/19 9:01 AM, John Paul Adrian Glaubitz wrote:
> Here's the log for running the testsuite on sh4 with kernel 3.16 and glibc
> 2.29,
> gcc-9 on real hardware (my SH7785LCR evaluation board). m68k is coming later.
Attaching the testsuite run for libffi 3.3-rc1 on my Amiga 4000/68060 r
Hi!
Here's the log for running the testsuite on sh4 with kernel 3.16 and glibc 2.29,
gcc-9 on real hardware (my SH7785LCR evaluation board). m68k is coming later.
It was invoked with:
$ ./configure && make -j2 && make check | tee ~/ffi-sh4.log
Adrian
--
.''`. John Paul Adrian Glaubitz
: :'
Hi!
On 10/31/19 9:47 PM, Anthony Green wrote:
> I was using that one, but I haven't been able to connect to it
> today, so I took it out for now. I'll try again later.
The machine is up and reachable:
glaubitz@zlogin2:~> ssh gcc202.fsffrance.org
Linux gcc202 4.19.0-5-sparc64-smp #1 SMP Debian
Hey John,
I was using that one, but I haven't been able to connect to it
today, so I took it out for now. I'll try again later.
libffi doesn't see a ton of activity, so I predict a light load...
but this an experiment and we'll see how it goes!
AG
On Thu, Oct 31, 2019 at 4:32 PM John Paul
Hi Anthony!
> On Oct 31, 2019, at 9:06 PM, Anthony Green wrote:
>
>
> I've figured out a way to use the GCC compile farm
> (https://cfarm.tetaneutral.net/) with travis-ci so real hardware builds/tests
> can participate in the travis-ci testing process.
(...)
> If anybody is willing to give
Green wrote:
>
>> > libffi 3.3 release candidate 1 is available for testing...
>> >
>> >
>> https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
>> > https://github.com/libffi/libffi/releases/tag/v3.3-rc1
>>
&
On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose wrote:On
24.10.19 13:16, Anthony Green wrote:
> > libffi 3.3 release candidate 1 is available for testing...
> >
> >
> https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
> > https://github
On Fri, Oct 25, 2019 at 6:08 AM Matthias Klose wrote:
> test results from
> https://buildd.debian.org/status/package.php?p=libffi&suite=experimental
Thank you, Matthias!
i386 (i686-linux-gnu), hurd-i386, kfreebsd-i386:
>
> Running ../../testsuite/libffi.bhaible/bhaible.exp ...
> FAIL: libffi.b
Hi,
On 10/25/19 10:04 PM, Andreas Schwab wrote:
On Okt 25 2019, John Paul Adrian Glaubitz wrote:
On 10/25/19 8:32 PM, Andreas Schwab wrote:
On Okt 25 2019, John Paul Adrian Glaubitz wrote:
It's qemu-user that we are using here, not qemu-system. qemu-user is more
finicky
when it comes to runn
On Okt 25 2019, John Paul Adrian Glaubitz wrote:
> On 10/25/19 8:32 PM, Andreas Schwab wrote:
>> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>>> It's qemu-user that we are using here, not qemu-system. qemu-user is more
>>> finicky
>>> when it comes to running testsuites.
>>
>> There is noth
On 10/25/19 9:04 PM, Andreas Schwab wrote:
> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>
>> On 10/25/19 8:32 PM, Andreas Schwab wrote:
>>> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
It's qemu-user that we are using here, not qemu-system. qemu-user is more
finicky
when
On Okt 25 2019, John Paul Adrian Glaubitz wrote:
> On 10/25/19 4:41 PM, Andreas Schwab wrote:
>> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>>
>>> It makes little sense to run these tests on qemu.
>>
>> If qemu cannot run these tests it is broken.
>
> It's qemu-user that we are using here,
On 10/25/19 8:32 PM, Andreas Schwab wrote:
> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>> It's qemu-user that we are using here, not qemu-system. qemu-user is more
>> finicky
>> when it comes to running testsuites.
>
> There is nothing finicky about this testsuite. It's pure user-space.
On Okt 25 2019, John Paul Adrian Glaubitz wrote:
> It makes little sense to run these tests on qemu.
If qemu cannot run these tests it is broken.
Andreas.
--
Andreas Schwab, sch...@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510 2552 DF73 E780 A9DA AEC1
"And now for something co
On 10/25/19 4:41 PM, Andreas Schwab wrote:
> On Okt 25 2019, John Paul Adrian Glaubitz wrote:
>
>> It makes little sense to run these tests on qemu.
>
> If qemu cannot run these tests it is broken.
It's qemu-user that we are using here, not qemu-system. qemu-user is more
finicky
when it comes t
On 10/25/19 12:08 PM, Matthias Klose wrote:
> On 24.10.19 13:16, Anthony Green wrote:
>> libffi 3.3 release candidate 1 is available for testing...
>>
>> https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
>> https://github.com/libffi/l
On 24.10.19 13:16, Anthony Green wrote:
libffi 3.3 release candidate 1 is available for testing...
https://github.com/libffi/libffi/releases/download/v3.3-rc1/libffi-3.3-rc1.tar.gz
https://github.com/libffi/libffi/releases/tag/v3.3-rc1
test results from
https://buildd.debian.org/status
17 matches
Mail list logo
