Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-05
Date: Tue, 7 Mar 2017 00:01:25 +0100	[thread overview]
Message-ID: <20170307000125.6516d2f9@free-electrons.com> (raw)
In-Reply-To: <20170306210032.GC3976@free.fr>

Hello,

Thanks for the analysis of those build failures! Some comments below.

On Mon, 6 Mar 2017 22:00:32 +0100, Yann E. MORIN wrote:

> >          arm |                 libepoxy-1.4.1 | NOK | http://autobuild.buildroot.net/results/48c35bac7cf674e2bc55f9bd53b905ad5e212258  
> 
> This is again caused by a mismatch between types defined by Khronos and
> those in odroid-mali.

These are gone, odroid-mali is marked as broken.

> >         i686 |                 libepoxy-1.4.1 | NOK | http://autobuild.buildroot.net/results/e29a22a2d9c81c87d271c2a6e7d041d36c370adc
> >         sh4a |                 libepoxy-1.4.1 | NOK | http://autobuild.buildroot.net/results/6cc1212728248d5443fe9a367b4aeb3807ce623e  
> 
> EGL not found...

Gustavo, could you have a look?

> 
> >      powerpc |                polarssl-1.2.19 | NOK | http://autobuild.buildroot.net/results/ab3565f6585e47573bcb62ef5e7250986c90d8e3  
> 
> Static linking issue: polarssl build a 'benchmark' utility that links
> with -lcrypto, which uses symbols fron libz, but libz is not pulled in
> in a static build.

polarssl should use pkg-config to discover OpenSSL.

> >          arm |                     putty-0.68 | NOK | http://autobuild.buildroot.net/results/3ade64119e327cc810282c1bcd89a8e7d229a73f
> >          arm |                     putty-0.68 | NOK | http://autobuild.buildroot.net/results/3c26267f46f0653f2d40e03e5e4212e58e7ce177  
> 
> Should be fixed by:
>     https://git.buildroot.org/buildroot/commit/?id=18275a0420fd39817ea01e30f5d815c78dc72cc0

Correct.

> >         i686 |                     qemu-2.8.0 | NOK | http://autobuild.buildroot.net/results/5a685a307678bbcfd87c6f1bd44b5648b4d397f9  
> 
> error: 'struct timex' has no member named 'tai'
> 
> uClibc toolchain: fields missing? Not available in uClibc?

This is fixed by 2ae688f0f0f79f54d1ca18824251cdc683e1a07f, but I
haven't rebuilt all the uClibc toolchains yet, I'll try to do so
tomorrow.

> >      powerpc |              rabbitmq-c-v0.8.0 | NOK | http://autobuild.buildroot.net/results/8ac322af1293eb195f2eab80bdfe1b87931948b6  
> 
> Static linking issue, again missing -lz.

Not only, there's also some missing -lintl.

The missing -lz can be fixed by using pkg-config to discover OpenSSL
(can be done by a person knowledgeable in CMake).

The missing -lintl is more annoying, because it's never encoded in .pc
files anyway.

> >          arc |                   samba4-4.5.5 | NOK | http://autobuild.buildroot.net/results/2e214d6b2de1008858f4129e8000dd1202302117  
> 
> This is caused by the ARC Synopsys toolchain which has a uClibc without
> support for quota.

We should add an exception then.

> >          arm |                    slang-2.3.0 | NOK | http://autobuild.buildroot.net/results/256ffb34fa890bae23ff39783006e0741e2abc49  
> 
> undefined reference to `tputs'
> 
> Static linking issue, needs to link against ncurses.

Does libreadline provide a pkg-config file?

> >          arm | vpnc-b1243d29e0c00312ead038... | NOK | http://autobuild.buildroot.net/results/16a7c30f0627c51b171ec71b2e7f24444e38526d  
> 
> undefined reference to `libintl_bindtextdomain'
> 
> Static linking issue, needs -lintl.

Yeah, this -lintl thing is really a pain. I'll try to work on a
proposal to get rid of it.

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2017-03-06 23:01 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-06  7:28 [Buildroot] [autobuild.buildroot.net] Build results for 2017-03-05 Thomas Petazzoni
2017-03-06 21:00 ` Yann E. MORIN
2017-03-06 23:01   ` Thomas Petazzoni [this message]
2017-03-07 13:51     ` Gustavo Zacarias
2017-03-07 19:18   ` Peter Seiderer

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=20170307000125.6516d2f9@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox