From: Rahul Bedarkar <Rahul.Bedarkar@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-23
Date: Fri, 26 Aug 2016 14:50:29 +0530 [thread overview]
Message-ID: <57C009DD.9070309@imgtec.com> (raw)
In-Reply-To: <20160824172543.19BA410CCE6@stock.ovh.net>
Hi Thomas,
On Wednesday 24 August 2016 10:55 PM, Thomas Petazzoni wrote:
> Hello,
>
> This is the list of Buildroot build failures that occured on
> 2016-08-23, and for which you are a registered architecture developer
> or package developer. Please help us improving the quality of
> Buildroot by investigating those build failures and sending patches to
> fix them. Thanks!
>
> Build failures related to your packages:
>
> bfin | glog-v0.3.4 | http://autobuild.buildroot.net/results/914cc267eba357cc0c425f07e57c6ae35b099b7e
>
We have disabled glog on blackfin external toolchain uclinux sometime
back [1]. But we are seeing same issue with buildroot based toolchain now.
As elf-fdpic.h is only provided by uClibc and we support only uClibc for
blackfin, should we disable glog on blackfin ?
Regards,
Rahul
[1] -
https://git.buildroot.net/buildroot/commit/?id=3b198722a5cfdf2ad5fd5a243aaa5f9f730b0101
next parent reply other threads:[~2016-08-26 9:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20160824172543.19BA410CCE6@stock.ovh.net>
2016-08-26 9:20 ` Rahul Bedarkar [this message]
2016-08-26 9:44 ` [Buildroot] [autobuild.buildroot.net] Your build results for 2016-08-23 Thomas Petazzoni
[not found] <20160824172543.21E4E10CE3A@stock.ovh.net>
2016-08-26 16:57 ` André Hentschel
2016-08-26 17:46 ` Thomas Petazzoni
[not found] <20160824172543.36D1D10CEEE@stock.ovh.net>
2016-08-26 23:43 ` Jörg Krause
2016-08-27 7:59 ` Thomas Petazzoni
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=57C009DD.9070309@imgtec.com \
--to=rahul.bedarkar@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.