From: "Jörg Krause" <joerg.krause@embedded.rocks>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-01-24
Date: Sun, 29 Jan 2017 21:37:34 +0100 [thread overview]
Message-ID: <1485722254.4549.1.camel@embedded.rocks> (raw)
In-Reply-To: <CAHXCMM+cL0UnnfhgFTtkeC7L+jRh8s=tr-U5CTC0YZxzUBb4bA@mail.gmail.com>
Hi Samuel,
On Thu, 2017-01-26 at 12:04 +0100, Samuel Martin wrote:
> Hi all,
>
> On Wed, Jan 25, 2017 at 10:15 PM, Baruch Siach <baruch@tkos.co.il>
> wrote:
> > Hi J?rg,
> >
> > On Wed, Jan 25, 2017 at 10:05:42PM +0100, J?rg Krause wrote:
> > > On Wed, 2017-01-25 at 08:30 +0100, Thomas Petazzoni wrote:
> > > [snip]
> > >
> > > > Detail of failures
> > > > ===================
> > > >
> > > > ????????i586 |????????????????bctoolbox-0.4.0 | NOK | http://au
> > > > tobuil
> > > > d.buildroot.net/results/4b4b00ad3b95ddacc9d5cc31c34e457ee55c936
> > > > 4
>
> Regarding this package, apologies I missed it during the initial
> review :s
Never mind! That's the autobuilder are there for, right?
> This build failure occurs because it goes in a path it should not.
> In the Config.in: it is mentionned that mbedtls is prefered to
> polarssl [1], hence the select [1] and the dependency in the *.mk
> [2].
> However, the cmake configure flags are not set accordingly to this,
> and the defaults may play against us [3].
>
> I would suggest to set the ENABLE_{MBEDTLS,POLARSSL} flags in the
> *.mk first.
> This should prevent from following this case [4], as displayed in the
> build log [5].
Support for PolarSSL is only enabled if mbedTLS is not found, but I
agree, it's better to disable it explicitly.
> After this, if the CheckSymbolExists still causes error, we may need
> to patch the bctoolbox
> cmake code to set/fix the variables used by CheckSymbolExists [6].
I prepared a patch of FindMbedTLS.cmake which checks if mbedtls was
build with libz support and if so, add libz to MBEDTLS_LIBRARIES. This
way, CMake should take care of linking against the libz in sysroot.
> > >
> > > 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.
> > >
> > > [..]/i586-buildroot-linux-musl/bin/ld: warning: libc.so.6, needed
> > > by
> > > /usr/lib32/libz.so.1, not found (try using -rpath or -rpath-link)
> > > /usr/lib32/libz.so.1: undefined reference to `strcpy at GLIBC_2.0'
> >
> > This is your host library.
> >
> > > I have no idea how to fix it. bctoolbox' cmakelists.txt does set
> > > CMAKE_INSTALL_RPATH=/usr/lib. Is this a problem?
> >
> > That is definitely not compatible with cross compilation.
> >
> > baruch
> >
> > --
> > ?????http://baruch.siach.name/blog/??????????????????~. .~???Tk
> > Open Systems
> > =}------------------------------------------------ooO--U--Ooo----
> > --------{=
> > ???- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.
> > il -
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
>
> Regards,
>
> [1] https://git.buildroot.net/buildroot/tree/package/bctoolbox/Config
> .in#n5
> [2] https://git.buildroot.net/buildroot/tree/package/bctoolbox/bctool
> box.mk#n11
> [3] https://github.com/BelledonneCommunications/bctoolbox/blob/master
> /CMakeLists.txt#L44
> [4] https://github.com/BelledonneCommunications/bctoolbox/blob/master
> /CMakeLists.txt#L88
> [5] http://autobuild.buildroot.net/results/4b4/4b4b00ad3b95ddacc9d5cc
> 31c34e457ee55c9364/build-end.log
> [6] https://cmake.org/cmake/help/v3.0/module/CheckSymbolExists.html
>
>
next prev parent reply other threads:[~2017-01-29 20:37 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 [this message]
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
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=1485722254.4549.1.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