From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-31
Date: Fri, 1 Aug 2014 15:30:57 +0100 [thread overview]
Message-ID: <53DBA4A1.6000808@imgtec.com> (raw)
In-Reply-To: <20140801162908.38353774@free-electrons.com>
On 08/01/2014 03:29 PM, Thomas Petazzoni wrote:
> Dear Vicente Olivert Riera,
>
> On Fri, 1 Aug 2014 15:20:56 +0100, Vicente Olivert Riera wrote:
>> On 08/01/2014 07:30 AM, Thomas Petazzoni wrote:
>>> Build statistics for 2014-07-31
>>> ===============================
>>> mips64el | libvncserver-0.9.9 | NOK | http://autobuild.buildroot.net/results/3bf952fe2e3ebd8308e8ac5001896474790249d9/
>>
>> I can't reproduce this failure. It should be a problem of the
>> autobuilder or maybe someone already fixed this bug.
>
> Yeah, the problem was not MIPS related at all here. Caused by the
> static linking and libtool changes we have been doing with Gustavo over
> the last 2 days. This issue is already fixed now.
>
>>
>>> mips | ltrace-0896ce554f80afdcba81... | NOK | http://autobuild.buildroot.net/results/081b58cae5ce05c32811a1d1d442e66828d9e73e/
>>
>> Reported upstream:
>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=756764
>
> Thanks. Maybe you should send a mail to the ltrace-devel mailing list.
> Even though the ltrace web site says to report bugs on the Debian bug
> track system, I am not sure the upstream maintainer of ltrace will
> actually look there, while he seems to be responsive on the mailing
> list.
I actually did both things :P
> But well, let's wait a few days and see if there's a reaction.
>
> Thanks!
>
> Thomas
>
--
Vincent
prev parent reply other threads:[~2014-08-01 14:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-07-31 Thomas Petazzoni
2014-08-01 14:20 ` Vicente Olivert Riera
2014-08-01 14:29 ` Thomas Petazzoni
2014-08-01 14:30 ` Vicente Olivert Riera [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=53DBA4A1.6000808@imgtec.com \
--to=vincent.riera@imgtec.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.