Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-02
Date: Fri, 3 Jan 2014 10:58:00 +0200	[thread overview]
Message-ID: <20140103085800.GO6589@tarshish> (raw)
In-Reply-To: <2683108.9dlVqoAHeN@sagittae>

Hi J?r?me,

On Fri, Jan 03, 2014 at 09:51:55AM +0100, J?r?me Pouiller wrote:
> On Fri 03 Jan 2014 09:45:04 Baruch Siach wrote:
> > On Fri, Jan 03, 2014 at 08:30:07AM +0100, Thomas Petazzoni wrote:
> > >     xtensa |                libcgicc-3.2.12 | NOK |
> > >     http://autobuild.buildroot.net/results/7ccbf088cac523f5cccc36d4b5edc3a45c670044/
> > The cause of this failure is that the static stdc++ library is not copied to
> > the toolchain sysroot. Manually copying
> > build/xtensa-buildroot-linux-uclibc/libstdc++-v3/src/.libs/libstdc++.a to
> > staging/usr/lib fixes the problem. Can someone point me at the code that
> > copies toolchain libraries to sysroot?
> I believe this patch should do the job:
>   http://patchwork.ozlabs.org/patch/282186/

Thanks. But in my case libstdc++.a does get built. It just not copied to 
staging. Do you thing your patch is still relevant?

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2014-01-03  8:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-03  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-01-02 Thomas Petazzoni
2014-01-03  7:45 ` Baruch Siach
2014-01-03  8:51   ` Jérôme Pouiller
2014-01-03  8:58     ` Baruch Siach [this message]
2014-01-03  9:52       ` Jérôme Pouiller
2014-01-03 12:01         ` Baruch Siach
2014-01-03 10:24       ` Gustavo Zacarias

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=20140103085800.GO6589@tarshish \
    --to=baruch@tkos.co.il \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox