From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-25
Date: Wed, 26 Feb 2014 21:57:40 +0100 [thread overview]
Message-ID: <20140226215740.4fd07066@skate> (raw)
In-Reply-To: <87k3cigt81.fsf@dell.be.48ers.dk>
Dear Peter Korsgaard,
On Wed, 26 Feb 2014 09:42:54 +0100, Peter Korsgaard wrote:
> > i686 | host-libxslt-1.1.28 | NOK | http://autobuild.buildroot.net/results/6dcef647eb0f0db7de3f34194eb15ceebc645b39/
>
> CCLD testThreads
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_code at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_auto_decoder at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_end at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_properties_decode at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_code at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_auto_decoder at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_end at XZ_5.0'
> /home/peko/scratch/host/usr/lib/libxml2.so: undefined reference to `lzma_properties_decode at XZ_5.0'
>
> Thomas, I think you looked into it and it was something about it picking
> up lzma from the build machine. Do you have a fix?
Yeah, probably need to explicitly disable lzma support from
host-libxml2, I'd say.
> > arm | ltp-testsuite-20130904 | NOK | http://autobuild.buildroot.net/results/722fea5a4a30c271a83cadf61e2d1e07bcb7a4ea/
>
> Ptrace issue:
>
> /home/test/test/1/output/host/usr/arm-buildroot-linux-gnueabi/sysroot/usr/include/linux/ptrace.h:58:8: error: redefinition of 'struct ptrace_peeksiginfo_args'
Maybe fixed by the ltp-testsuite bump in -next.
> > powerpc | mmc-utils-11f2ceabc4ad3f0dd... | NOK | http://autobuild.buildroot.net/results/fa45d93d145f3991e9c8bb99997b7e41cedc64b0/
>
> Too old kernel headers?
Yes.
>
> mmc.h:18:29: fatal error: linux/mmc/ioctl.h: No such file or directory
> > powerpc | sysklogd-1.5 | NOK | http://autobuild.buildroot.net/results/88d76be91d04a22dd2f1683396a172be085e1657/
>
> Internal compiler error. Thomas, how old is this ctng toolchain?
Fairly old. Yann has provided me some newer ctng toolchains, but he has
used "br" as the vendor part of the tuple, which I find highly
confusing, so I haven't put in "production" these newer ctng toolchains.
> > powerpc | xlib_libXau-1.0.8 | NOK | http://autobuild.buildroot.net/results/f62f8e63082fdfb9a68c8b4e629e5a7fa02b3bba/
>
> Out of memory?
>
> configure: creating ./config.status
> ./config.status: fork: Cannot allocate memory
Crappy build machine :-)
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-02-26 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-26 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-25 Thomas Petazzoni
2014-02-26 8:42 ` Peter Korsgaard
2014-02-26 11:00 ` Gustavo Zacarias
2014-02-26 20:57 ` Thomas Petazzoni [this message]
2014-02-26 21:01 ` Peter Korsgaard
2014-02-26 21:04 ` 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=20140226215740.4fd07066@skate \
--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