From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24
Date: Tue, 07 Feb 2017 14:00:39 +0100 [thread overview]
Message-ID: <1486472439.1692.3.camel@embedded.rocks> (raw)
In-Reply-To: <CAHXCMMJ-HNK9mCC8_cf1Fk4CnX7NCGF9ypWBVCu2JeBa5oK8CQ@mail.gmail.com>
Hi Samuel,
On Tue, 2017-02-07 at 12:28 +0100, Samuel Martin wrote:
> J?rg, all,
>
> On Tue, Feb 7, 2017 at 12:38 AM, J?rg Krause
> <joerg.krause@embedded.rocks> wrote:
> > Hi Samuel,
> >
[snip]
> >
> > Version 3.6.3 works, too. So, I did a git bisect. The rpath issue
> > was
> > introduced in "Teach find_library and find_package to search lib32
> > paths" [1].
>
> Thanks for the investigation!
>
> >
> > Any ideas how to fix this?
>
> Not so far :-/
Ray Donnely proposed a potential fix for this issue [1] on the CMake
mailing list. I have not tried the patch so far.
> Could you apply this change, run (from an already populated build
> tree, no need to restart the build from scratch):
> ? $ make mbedtls-dirclean mbedtls-configure 2>&1 | tee mbedtls-
> configure.log
>
> and pastebin/share the mbedtls-configure.log file?
Sorry, but I don't understand. Which change do you mean? Should I run
this on the Debian (bctoolbox build error is reproducable) or the Arch
(bctoolbox build error is not reproducable) host? Which CMake version
should I use?
[1] https://gitlab.kitware.com/mingwandroid/cmake/commit/b937ff949d8fda
ab7d8b812d503f67f8cef69532
J?rg
next prev parent reply other threads:[~2017-02-07 13:00 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
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 [this message]
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=1486472439.1692.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