From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24
Date: Mon, 30 Jan 2017 20:59:02 +0100 [thread overview]
Message-ID: <1485806342.3759.3.camel@embedded.rocks> (raw)
In-Reply-To: <20170129211155.f6sebtrdmsrwb2yw@tarshish>
Hi Baruch,
On Sun, 2017-01-29 at 23:11 +0200, Baruch Siach wrote:
> Hi J?rg,
>
> On Sun, Jan 29, 2017 at 09:37:34PM +0100, J?rg Krause wrote:
> > On Thu, 2017-01-26 at 12:04 +0100, Samuel Martin wrote:
> > > On Wed, Jan 25, 2017 at 10:15 PM, Baruch Siach <baruch@tkos.co.il
> > > >
> > > wrote:
> > > > On Wed, Jan 25, 2017 at 10:05:42PM +0100, J?rg Krause wrote:
> > > > > Unfortunately I cannot reproduce this issue. Is it a rpath
> > > > > issue?
> > > > > cmake links a test program with host zlib:
> > >
> > > Note: I'm not able to reproduce the error either.
> >
> > I wonder, what makes the difference to be able to reproduce the
> > issue.
>
> See http://lists.busybox.net/pipermail/buildroot/2017-January/182237.
> html.
I setup a Debian and Scientific Linux system yesterday, but I still
cannot reproduce the build issue. However, I've found out that mbedlts
is never build with zlib support in Buildroot [1].
[1] http://patchwork.ozlabs.org/patch/721218/
next prev parent reply other threads:[~2017-01-30 19:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-25 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24 Thomas Petazzoni
2017-01-25 21:05 ` Jörg Krause
2017-01-25 21:15 ` Baruch Siach
2017-01-26 11:04 ` Samuel Martin
2017-01-26 11:11 ` Baruch Siach
2017-01-26 11:14 ` Jörg Krause
2017-01-26 11:28 ` Baruch Siach
2017-01-29 20:37 ` Jörg Krause
2017-01-29 21:11 ` Baruch Siach
2017-01-30 19:59 ` Jörg Krause [this message]
2017-01-30 21:20 ` Baruch Siach
2017-01-30 21:22 ` Jörg Krause
2017-01-30 21:26 ` Baruch Siach
2017-01-30 21:45 ` Jörg Krause
2017-02-05 22:17 ` Jörg Krause
2017-02-06 11:06 ` Thomas Petazzoni
2017-02-06 16:52 ` Samuel Martin
2017-02-06 17:43 ` Jörg Krause
2017-02-06 17:53 ` Samuel Martin
2017-02-06 17:59 ` Jörg Krause
2017-02-06 18:14 ` Samuel Martin
2017-02-06 19:24 ` Jörg Krause
2017-02-06 21:12 ` Jörg Krause
2017-02-06 23:38 ` Jörg Krause
2017-02-07 11:28 ` Samuel Martin
2017-02-07 13:00 ` Jörg Krause
2017-02-07 13:29 ` Samuel Martin
2017-02-07 19:07 ` Jörg Krause
2017-02-09 20:02 ` Jörg Krause
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=1485806342.3759.3.camel@embedded.rocks \
--to=joerg.krause@embedded.rocks \
--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