From: Simon Marchi <simon.marchi@ericsson.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: Re: buildbot: Fedora-i686 configuration problem
Date: Fri, 10 Jul 2015 17:29:00 -0000 [thread overview]
Message-ID: <55A0010F.2030306@ericsson.com> (raw)
In-Reply-To: <87a8v4hswd.fsf@redhat.com>
On 15-07-10 12:36 PM, Sergio Durigan Junior wrote:
> On Friday, July 10 2015, I wrote:
>
>> On Friday, July 10 2015, Simon Marchi wrote:
>>
>>> Hi Sergio,
>>>
>>> This builder seems to have a lot of difficulty finding gcc during configure.
>>>
>>> http://gdb-build.sergiodj.net/builders/Fedora-i686
>>>
>>> Slaves 3 and 4 seem to have this problem. The build that passed was on slave 1,
>>> so that one seems ok. I don't know about 2.
>>
>> Hey Simon,
>>
>> Thanks for the message. Yesterday I set up a new buildslave and it's
>> still not 100% configured for 32-bit builds :-/. Bummer. I will fix
>> that ASAP today.
>
> It should be working OK now.
>
> Thanks,
Ok, thank you very much!
prev parent reply other threads:[~2015-07-10 17:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-10 13:13 Simon Marchi
2015-07-10 16:06 ` Sergio Durigan Junior
2015-07-10 16:36 ` Sergio Durigan Junior
2015-07-10 17:29 ` Simon Marchi [this message]
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=55A0010F.2030306@ericsson.com \
--to=simon.marchi@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=sergiodj@redhat.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