[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Gm2] Build of 04-Nov-2014 tarball of 4.7.3 on Ubuntu 14.04 on x86_6
From: |
Gaius Mulley |
Subject: |
Re: [Gm2] Build of 04-Nov-2014 tarball of 4.7.3 on Ubuntu 14.04 on x86_64 |
Date: |
Tue, 09 Dec 2014 11:56:37 +0000 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/24.4 (gnu/linux) |
JD <address@hidden> writes:
> On 02/12/14 17:00, address@hidden wrote:
>>> Gaius,
>>> This is my result:
>>> === gm2 Summary ===
>>>
>>> # of expected passes 7771
>>> # of unexpected failures 1477
>>> # of unresolved testcases 546
>>> make: [check-gm2] Error 1 (ignored)
>>>
>>> real 17m52.221s
>>> user 13m47.080s
>>> sys 3m31.943s
>>>
>>> I've included the timings to show off my new Core i5 PC!
>>>
>>> As the system is completely new the results are likely to have
>>> suffered from some installs not being done. I took the list from the
>>> gm2 website and added libpth-dev, dejagnu and flex. Can you think of
>>> any other ones?
>>>
>>> Regards,
>>> John
>> Hi John,
>>
>> if the make ran to completion I'd assume that all required packages were
>> installed. The tests require libpth-dev, you could try installing gm2
>> and setting your path to the installed location and running the dejagnu
>> tests (although in theory this shouldn't be necessary - you do seem to
>> be getting a huge number of failures).
>>
>> I'm currently working on the shared library linking, and modifying it
>> to coexist with libtool.
>>
>> regards,
>> Gaius
>>
> Gaius,
> Yes, that is much better:
>
> === gm2 Summary ===
>
> # of expected passes 7970
> # of unexpected failures 114
> # of unresolved testcases 6
>
> I did: runtest --tool gm2 in directory ~/GM2/scratch-area/build-4.7.3/gcc.
>
> John
>
Hi John,
thanks for the report - it appears there are some incorrect gm2 paths
being set during the dejagnu - will look into it!
regards,
Gaius