From: nick <xerofoify@gmail.com>
To: Jonathan Wakely <jwakely.gcc@gmail.com>
Cc: GCC help <gcc-help@gcc.gnu.org>
Subject: Re: Tests Failing on x86_64_gnu
Date: Mon, 29 Oct 2018 21:40:00 -0000 [thread overview]
Message-ID: <fae9946f-6f78-0e35-e65f-fda430c31c9c@gmail.com> (raw)
In-Reply-To: <CAH6eHdQ4Cdch6Y6oTRfhZYYcTVk6kAB7Erh7wL0MhaJYsWsNSQ@mail.gmail.com>
On 2018-10-29 4:44 p.m., Jonathan Wakely wrote:
> Please reply to the mailing list, not just to me.
>
>
Sorry thought it was sent to the list.
Nick
> On Mon, 29 Oct 2018 at 20:14, nick <xerofoify@gmail.com> wrote:
>>
>>
>>
>> On 2018-10-29 3:31 p.m., Jonathan Wakely wrote:
>>> On Mon, 29 Oct 2018 at 18:05, nick <xerofoify@gmail.com> wrote:
>>>>
>>>> Greetings,
>>>>
>>>> I just build,configuring and ran the tests from the upstream gcc git repo like this:
>>>> mdkir odbjir
>>>> cd obdjir
>>>> $PWD/../gcc/configure --prefix=$HOME/GCC-deve
>>>> make -j8
>>>> make bootstrapq
>>>
>>> This is redundant, just saying "make" does the same thing.
>>>
>>>> make -k check
>>>>
>>>> Those are the steps from the offical docs unless I am missing a step i.e. does
>>>> make install need to be done or not?
>>>
>>> Done for what? It needs to be done to install the compiler you just
>>> built, but not to test it.
>>>
>>>> Don't know if this a reported issue or not.
>>>
>>> You haven't said what the issue is, so we can't say.
>>>
>> Jonathan,
>> The issues is after the above commands including make -k check it fails the tests on
>> on a Ubuntu 18.04, x86_64_gnu based system for the mainline git repo. I tried it
>> clean with the above steps and it fails including reporting a few unexpected failures.
>> Those steps above are the steps I ran in order to build and test it on a clean gcc without
>> anything else and it fails. I will run the tests again just to see if something is using too much
>> memory and making it fail as that may be the case but I doubt it.
>>
>> Sorry for the confusion,
>> Nick
next prev parent reply other threads:[~2018-10-29 21:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 18:05 nick
2018-10-29 19:31 ` Jonathan Wakely
[not found] ` <cffe3f0e-f5c9-e6b5-f5b2-4e7f7aecf07d@gmail.com>
[not found] ` <CAH6eHdQ4Cdch6Y6oTRfhZYYcTVk6kAB7Erh7wL0MhaJYsWsNSQ@mail.gmail.com>
2018-10-29 21:40 ` nick [this message]
2018-10-29 21:45 ` Jonathan Wakely
[not found] ` <9d341128-5aec-e760-88ac-c243724d40e1@gmail.com>
2018-10-29 22:19 ` Jonathan Wakely
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fae9946f-6f78-0e35-e65f-fda430c31c9c@gmail.com \
--to=xerofoify@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=jwakely.gcc@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).