From: Rodrigo Rebello <rprebello@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-05-16
Date: Tue, 17 May 2016 10:53:02 -0300 [thread overview]
Message-ID: <CABLs7GV7ohYiPxGzn=2mp=U_jfUS66Q2HvEm6q0jDiiQuijh4w@mail.gmail.com> (raw)
In-Reply-To: <20160517153611.2a3b4199@free-electrons.com>
Thomas,
2016-05-17 10:36 GMT-03:00 Thomas Petazzoni
<thomas.petazzoni@free-electrons.com>:
[snip]
>> arm | chocolate-doom-2.2.1 | NOK | http://autobuild.buildroot.net/results/31ec8fed2390b8fece70ec7168019c736fe66b01/
>
> This is a long-standing issue of static linking with chocolate-doom, it
> forgets to link with libstdc++. Rodrigo, you contributed this package,
> and already fixed some static linking issues with it. Can you look at
> this one, or alternatively decide that we don't want to support static
> linking for chocolate-doom?
>
Sure. I'll have a look into it later when I get back from work.
Regards,
Rodrigo
next prev parent reply other threads:[~2016-05-17 13:53 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-17 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-16 Thomas Petazzoni
2016-05-17 13:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-17 13:53 ` Rodrigo Rebello [this message]
2016-05-17 15:13 ` gwenhael.goavec
2016-05-17 15:20 ` Thomas Petazzoni
2016-05-18 7:09 ` gwenhael.goavec
2016-05-18 19:40 ` Arnout Vandecappelle
2016-05-18 21:54 ` Thomas Petazzoni
2016-05-18 22:15 ` Arnout Vandecappelle
2016-05-17 16:27 ` Bernd Kuhls
2016-05-17 18:47 ` Bernd Kuhls
2016-05-17 18:56 ` Geoff Levand
2016-05-17 19:34 ` Thomas Petazzoni
2016-05-17 20:15 ` Geoff Levand
2016-05-17 21:03 ` Yegor Yefremov
2016-05-17 21:06 ` Yegor Yefremov
2016-05-18 19:33 ` Samuel Martin
2016-05-19 13:26 ` Gustavo Zacarias
2016-05-19 18:52 ` Gustavo Zacarias
2016-05-19 21:31 ` Arnout Vandecappelle
2016-05-20 7:35 ` Thomas Petazzoni
2016-05-25 14:44 ` Clayton Shotwell
2016-06-17 1:21 ` Ben Boeckel
2016-06-17 2:11 ` Ben Boeckel
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='CABLs7GV7ohYiPxGzn=2mp=U_jfUS66Q2HvEm6q0jDiiQuijh4w@mail.gmail.com' \
--to=rprebello@gmail.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.